Triple
T341397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPEC |
E6844
|
entity |
| Predicate | headquartersMovedOn |
P12036
|
FINISHED |
| Object | 1965 |
—
|
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: 1965 | Statement: [OPEC, headquartersMovedOn, 1965]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headquartersMovedOn Context triple: [OPEC, headquartersMovedOn, 1965]
-
A.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
B.
temporaryHeadquartersLocation
Indicates the location where an entity is serving as a temporary headquarters for an organization or operation.
-
C.
relocatedToWashingtonYear
Indicates the year in which an entity moved or was transferred to Washington as its new location.
-
D.
temporaryHeadquartersFrom
Indicates that an entity serves as a temporary headquarters for another entity starting from a specified point in time.
-
E.
temporaryHeadquartersTo
Indicates a relationship where one entity serves as the temporary headquarters or central operating location for another entity.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae611f88190955fbebe2b01835b |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95197fc8190820e8ebd0d7d27fa |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea0a4c448190a8a179daa9b90645 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.