Triple
T24981803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tola son of Puah |
E625187
|
entity |
| Predicate | predecessorAsJudge |
P80319
|
FINISHED |
| Object | Abimelech |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Abimelech | Statement: [Tola son of Puah, predecessorAsJudge, Abimelech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorAsJudge Context triple: [Tola son of Puah, predecessorAsJudge, Abimelech]
-
A.
precededByAsChiefJudge
chosen
Indicates that one chief judge held the position immediately before another chief judge.
-
B.
predecessorCourtMentioned
Indicates that a court explicitly refers to or cites a decision from a predecessor court in its reasoning or judgment.
-
C.
presidingJudgeFrom
Indicates that a particular judge is serving as the presiding judge in a case, proceeding, or jurisdiction originating from a specified place or institution.
-
D.
predecessorInSuit
Indicates that one item directly precedes another in an ordered sequence within the same suit or category.
-
E.
hasPrincipalJudge
Indicates that one entity serves as the main or presiding judge for another entity, such as a court or judicial body.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 6:02 a.m.