Triple
T16199902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Design Capital 2014 |
E393168
|
entity |
| Predicate | selectionAnnouncedIn |
P81554
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [World Design Capital 2014, selectionAnnouncedIn, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionAnnouncedIn Context triple: [World Design Capital 2014, selectionAnnouncedIn, 2011]
-
A.
selectedAt
chosen
Indicates that an entity was chosen or picked at a specific point in time or under particular selection conditions.
-
B.
selectedTo
Indicates that one entity has been chosen or designated from a set of candidates to perform a role, receive something, or participate in an activity in relation to another entity.
-
C.
selectionMadeBy
Indicates that a particular choice or selection was performed or decided by a specific agent or entity.
-
D.
selectionFrom
Indicates that one entity is chosen as a member or subset from a larger set or collection represented by another entity.
-
E.
selectionShow
Indicates that a particular selection or choice is being displayed or made visible.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22709b0d88190b40787e0520d02ab |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.