Triple
T25781806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Invictus Games |
E649309
|
entity |
| Predicate | hasEditionLocation |
P115435
|
FINISHED |
| Object | London, United Kingdom |
—
|
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: London, United Kingdom | Statement: [Invictus Games, hasEditionLocation, London, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEditionLocation Context triple: [Invictus Games, hasEditionLocation, London, United Kingdom]
-
A.
notableEditionLocation
Indicates the place where a particularly significant or notable edition of a work was produced, published, or is held.
-
B.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
-
C.
hasEditionType
Indicates that one entity is a specific edition type or format classification of another entity (such as a work, publication, or product).
-
D.
hasPublicationPlace
chosen
Indicates the place or location where a publication was produced, issued, or made publicly available.
-
E.
hasEditionFeature
Indicates that one edition of a work includes a specific feature, characteristic, or component that distinguishes it from other editions.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 22, 2026, 5:39 a.m.