Triple
T37556362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations General Assembly resolution 45/155 |
E933707
|
entity |
| Predicate | designatedLocation |
P155476
|
FINISHED |
| Object | Vienna |
—
|
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 | Statement: [United Nations General Assembly resolution 45/155, designatedLocation, Vienna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatedLocation Context triple: [United Nations General Assembly resolution 45/155, designatedLocation, Vienna]
-
A.
designLocation
Indicates the place or setting where something is conceived, planned, or designed.
-
B.
designedForLocation
Indicates that something has been created or configured specifically to be used in, or suited to, a particular location.
-
C.
plannedLocation
Indicates the intended or scheduled location where an entity is expected to be or an event is planned to occur.
-
D.
assignedLocation
chosen
Indicates that a specific location has been designated or allocated to an entity as its place for presence, use, or operation.
-
E.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
Created at: May 3, 2026, 4:17 p.m.