Triple
T15384650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoshi Valley |
E367886
|
entity |
| Predicate | positionDisplay |
P116310
|
FINISHED |
| Object | question mark in Mario Kart 64 |
—
|
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: question mark in Mario Kart 64 | Statement: [Yoshi Valley, positionDisplay, question mark in Mario Kart 64]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionDisplay Context triple: [Yoshi Valley, positionDisplay, question mark in Mario Kart 64]
-
A.
currentDisplayLocation
chosen
Indicates the location or context where something is presently being shown or rendered.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
positionInShow
Indicates the specific order or placement an entity occupies within a show, series, or sequence of performances or episodes.
-
D.
positionNumber
Indicates the specific ordinal or identifying number assigned to a position within an ordered set or organizational structure.
-
E.
positionSought
Indicates the specific role, job, or position that an entity is aiming to obtain or apply for.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7397188190bde42b897ab4b5b4 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.