Triple
T28107195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Istanbul Park |
E710395
|
entity |
| Predicate | turn8Description |
P164041
|
FINISHED |
| Object | long multi-apex left-hander |
—
|
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: long multi-apex left-hander | Statement: [Istanbul Park, turn8Description, long multi-apex left-hander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turn8Description Context triple: [Istanbul Park, turn8Description, long multi-apex left-hander]
-
A.
8thHoleName
Indicates the name assigned to the eighth hole in a golf course or similar sequential layout.
-
B.
eighthStation
Indicates that one entity is the eighth stop, stage, or position in a sequential series or ordered process relative to another.
-
C.
8thHolePar
Indicates that the par (expected number of strokes) is specified for the 8th hole of a golf course.
-
D.
turningCircle
Indicates the radius or size of the circular path an object follows when it turns, typically reflecting how tightly it can change direction.
-
E.
upperDeckLanes
Indicates that the related entities are lanes located on the upper deck level of a multi-level structure (such as a roadway, bridge, or parking facility).
- F. None of above. chosen
Provenance (4 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 9:09 p.m.