Triple
T36853067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indianapolis 500: The Simulation |
E910720
|
entity |
| Predicate | simulationAspect |
P61123
|
FINISHED |
| Object | suspension behavior |
—
|
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: suspension behavior | Statement: [Indianapolis 500: The Simulation, simulationAspect, suspension behavior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: simulationAspect Context triple: [Indianapolis 500: The Simulation, simulationAspect, suspension behavior]
-
A.
testsAspect
Indicates that one entity evaluates, examines, or assesses a particular aspect, feature, or dimension of another entity.
-
B.
coversAspect
chosen
Indicates that one entity addresses, includes, or deals with a particular aspect or facet of another entity or topic.
-
C.
symbolicAspect
Indicates that one entity functions as a symbol or emblem that represents, expresses, or conveys a particular meaning, quality, or concept of another entity.
-
D.
simulationDomain
Indicates the conceptual or physical area, context, or scope within which a simulation is defined and executed.
-
E.
simulationMethod
Indicates the technique or approach used to perform or implement a simulation.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.