Triple
T36715820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Venezuela |
E906909
|
entity |
| Predicate | previousVersionAdoptedOn |
P200744
|
FINISHED |
| Object | 1954-02-17 |
—
|
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: 1954-02-17 | Statement: [Flag of Venezuela, previousVersionAdoptedOn, 1954-02-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousVersionAdoptedOn Context triple: [Flag of Venezuela, previousVersionAdoptedOn, 1954-02-17]
-
A.
previousVersionAdopted
Indicates that one entity has been adopted or implemented as a successor to an earlier version represented by the other entity.
-
B.
previousVersionInUseUntil
Indicates that an earlier version of something continued to be actively used up to a specified point in time.
-
C.
previousVersionLocationOfAdoption
Indicates that one entity is the location where an earlier or prior version of another entity was adopted.
-
D.
previousVersionUsedFrom
Indicates that one entity was used as the immediately preceding version from which another entity was derived or updated.
-
E.
previousVersionModified
Indicates that a newer version of an entity has been created by modifying the specified previous version.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffaa7bc45c8190b907db8579244a7b |
completed | May 9, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69ffa9f6c9a481908fbd4d18b311cbe2 |
completed | May 9, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69ffaa7af814819095ed51ea1989ff14 |
completed | May 9, 2026, 9:43 p.m. |
Created at: May 3, 2026, 4:12 p.m.