Triple
T27172943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secretary-General of Hezbollah |
E682967
|
entity |
| Predicate | termStartOfThirdHolder |
P89783
|
FINISHED |
| Object | 1992 |
—
|
LITERAL FINISHED |
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: 1992 | Statement: [Secretary-General of Hezbollah, termStartOfThirdHolder, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termStartOfThirdHolder Context triple: [Secretary-General of Hezbollah, termStartOfThirdHolder, 1992]
-
A.
termStartOfSecondHolder
Indicates that the term or tenure being referred to marks the beginning of the second holder’s period in that role or relationship.
-
B.
thirdOfficeHolderStartDate
chosen
Indicates the date on which the third person to hold a particular office or position began their term.
-
C.
officeHolderStartTime
Indicates the date and time at which an individual begins holding a particular office or position.
-
D.
thirdHolder
Indicates that an entity serves as the third holder or possessor of another entity in a sequence or ordered set of holders.
-
E.
thirdOfficeHolderEndDate
Indicates the date on which the third person to hold a particular office or position ended their term.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 9:24 a.m.