Triple
T881085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East African Community |
E19027
|
entity |
| Predicate | reEstablished |
P9113
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [East African Community, reEstablished, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reEstablished Context triple: [East African Community, reEstablished, 2000]
-
A.
reconstructedAfter
Indicates that one entity has been rebuilt, restored, or reassembled following the occurrence or existence of another entity or event.
-
B.
reopenedAfterReconstruction
Indicates that a place or facility resumed operations after undergoing reconstruction or major rebuilding work.
-
C.
reintroduced
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
-
D.
recreated
Indicates that an entity has been created again or restored, typically after being removed, destroyed, or significantly altered.
-
E.
reestablishedInYear
chosen
Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
- 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_69a4939c32488190a7ccd41cf0abb22b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4accb653c81909fe0753f78145be9 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8eca748190b58e0f08b30fba43 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.