Triple
T20322162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Office at Geneva |
E492231
|
entity |
| Predicate | openedAsUNOffice |
P6141
|
FINISHED |
| Object | 1946 |
—
|
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: 1946 | Statement: [United Nations Office at Geneva, openedAsUNOffice, 1946]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsUNOffice Context triple: [United Nations Office at Geneva, openedAsUNOffice, 1946]
-
A.
openedAsEmbassy
Indicates that a diplomatic mission or office was formally inaugurated and began operating with the status of an embassy.
-
B.
openedAs
chosen
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
C.
openedAsGovernorGeneralOffice
Indicates that an entity was inaugurated or began operation in the capacity of a Governor General’s office.
-
D.
hasUNOrgan
Indicates that an entity is a member of, affiliated with, or otherwise formally associated with a specified United Nations body or organ.
-
E.
openingByOffice
Indicates that an office or administrative unit is responsible for initiating or formally opening something (such as a case, process, or record).
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778c4430819083b17da5067b88ef |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:20 a.m.