Triple
T32756103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahmad bin Yahya |
E837624
|
entity |
| Predicate | reignEndResult |
P2721
|
FINISHED |
| Object | establishment of the Yemen Arab Republic |
—
|
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: establishment of the Yemen Arab Republic | Statement: [Ahmad bin Yahya, reignEndResult, establishment of the Yemen Arab Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignEndResult Context triple: [Ahmad bin Yahya, reignEndResult, establishment of the Yemen Arab Republic]
-
A.
endOfReign
chosen
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
B.
latestReignEnd
Indicates the date or time when the most recent reign or period of rule by an entity came to an end.
-
C.
reignClaimedEnd
Indicates the point in time or event at which a previously asserted or claimed reign or rule is considered to have ended.
-
D.
reignAsHeirApparentEnd
Indicates the point in time or event at which an individual’s period of serving as heir apparent to a throne or title comes to an end.
-
E.
reignAfter
Indicates that one entity begins its reign or rule following the conclusion of another entity's reign.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 1, 2026, 1:12 a.m.