Triple
T9299560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flag of Tuvalu |
E223723
|
entity |
| Predicate | temporarilyReplacedIn |
P24986
|
FINISHED |
| Object | 1995 |
—
|
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: 1995 | Statement: [flag of Tuvalu, temporarilyReplacedIn, 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporarilyReplacedIn Context triple: [flag of Tuvalu, temporarilyReplacedIn, 1995]
-
A.
replacedDuring
chosen
Indicates that one entity took the place of another entity during a specified time period or interval.
-
B.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
C.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
D.
replacedInProduct
Indicates that one component or element in a product has been substituted or superseded by another component or element within that product.
-
E.
replacedAtPar
Indicates that one entity has been replaced by another at a specific location or position within a larger structure or sequence.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08d070c881908bed41aada6f85ae |
completed | April 1, 2026, noon |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.