Triple
T25822930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Member States of UNIDO |
E650447
|
entity |
| Predicate | headquartersRepresentationAt |
P129113
|
FINISHED |
| Object | Vienna, Austria |
—
|
NE NERFINISHED |
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: Vienna, Austria | Statement: [Member States of UNIDO, headquartersRepresentationAt, Vienna, Austria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headquartersRepresentationAt Context triple: [Member States of UNIDO, headquartersRepresentationAt, Vienna, Austria]
-
A.
headquartersAt
chosen
Indicates that an organization’s main administrative center or primary office is located at a specified place.
-
B.
headquartersOfOffice
Indicates that a particular location serves as the main headquarters for a specified office or organizational unit.
-
C.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
D.
headquartersFor
Indicates that a location serves as the main administrative center or base of operations for an organization or entity.
-
E.
headquartersSuccessorOrganizationLocation
Indicates that the location served as the headquarters for a successor organization that followed a previous entity.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60192afc881908dd64d8024d75329 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 7:30 a.m.