Triple
T27172942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secretary-General of Hezbollah |
E682967
|
entity |
| Predicate | termEndOfSecondHolder |
P163911
|
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, termEndOfSecondHolder, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termEndOfSecondHolder Context triple: [Secretary-General of Hezbollah, termEndOfSecondHolder, 1992]
-
A.
termEndOfLastHolder
Indicates that something marks the end point of the term or tenure of the most recent previous holder of a role, position, or asset.
-
B.
secondTermEnd
Indicates that the referenced time or event marks the conclusion of the second term in a sequence of terms.
-
C.
secondSessionEndTime
Indicates the time at which the second session concludes.
-
D.
secondPhaseEndTime
Indicates the time at which the second phase of a process or event concludes.
-
E.
firstHolderEnd
Indicates that the specified entity is the one who initially held something and that this holding relationship has come to an end.
- F. None of above. chosen
Provenance (4 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_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 9:24 a.m.