Triple
T15535104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luigi Circuit |
E370319
|
entity |
| Predicate | hasStartingPosition |
P77379
|
FINISHED |
| Object | player karts line up on grid |
—
|
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: player karts line up on grid | Statement: [Luigi Circuit, hasStartingPosition, player karts line up on grid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStartingPosition Context triple: [Luigi Circuit, hasStartingPosition, player karts line up on grid]
-
A.
hasStartingArea
Indicates that an entity is associated with, or begins from, a specific initial area or region.
-
B.
initiatingPosition
chosen
Indicates the starting location or initial spatial position from which an action, process, or movement begins.
-
C.
hasTimeStart
Indicates that an event, process, or state begins at a specific point in time.
-
D.
initiallyPositionedAs
Indicates that one entity’s starting or original position is specified relative to another entity or reference frame.
-
E.
hasPositionOn
Indicates that one entity occupies or holds a specific role, job, or spatial location relative to another entity.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442e327c8190b4b879c8a3cd38e3 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.