Triple
T4412950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meydan grandstand complex |
E94892
|
entity |
| Predicate | hasSurfaceView |
P854
|
FINISHED |
| Object | dirt track |
—
|
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: dirt track | Statement: [Meydan grandstand complex, hasSurfaceView, dirt track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfaceView Context triple: [Meydan grandstand complex, hasSurfaceView, dirt track]
-
A.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
-
B.
hasView
chosen
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
-
C.
hasImageSurface
Indicates that one entity possesses or is associated with a surface suitable for displaying or bearing an image.
-
D.
hasSurfaceConnection
Indicates that two entities are directly connected or in contact at their surfaces, allowing interaction or continuity between them.
-
E.
hasSurfaceBody
Indicates that one entity possesses or is characterized by a particular surface or outer body.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b354e7b30c819082ee781dd202dcc4 |
completed | March 13, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69b34f5d0c54819085c08533bb58030a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.