Triple
T25374759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flag of Benin |
E633027
|
entity |
| Predicate | predecessorUsedUntil |
P162878
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [flag of Benin, predecessorUsedUntil, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorUsedUntil Context triple: [flag of Benin, predecessorUsedUntil, 1990]
-
A.
predecessorUsedFrom
Indicates that something was used or derived from a preceding version, state, or entity that came before it.
-
B.
predecessorNameUsage
Indicates that a name was used previously and has been replaced or superseded by a subsequent name in a sequence or lineage.
-
C.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
D.
predecessorVersion
Indicates that one entity is an earlier or prior version in a version sequence relative to another entity.
-
E.
predecessorStartDate
Indicates that the start date of one entity directly follows or is constrained by the start date of its predecessor entity in a sequence or dependency chain.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f62e83045c8190a424a2e401a88e9e |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d886828819080ec2f742b9449e3 |
completed | May 2, 2026, 4:59 p.m. |
Created at: April 21, 2026, 1:38 p.m.