Triple
T5908822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brickyard 400 |
E131408
|
entity |
| Predicate | timingSystem |
P21771
|
FINISHED |
| Object | electronic timing and scoring |
—
|
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: electronic timing and scoring | Statement: [Brickyard 400, timingSystem, electronic timing and scoring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timingSystem Context triple: [Brickyard 400, timingSystem, electronic timing and scoring]
-
A.
timeSystem
Indicates a relationship where an entity uses, follows, or is defined within a particular system for measuring or organizing time.
-
B.
timingStandard
Indicates that one entity specifies or conforms to the timing rules, constraints, or reference schedule defined by another entity.
-
C.
timingMethod
chosen
Indicates the method or technique used to measure or record the timing of an event or process.
-
D.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
-
E.
timeLoopMechanism
Indicates a relationship where events or states are repeatedly reset or cycled through the same temporal sequence due to a mechanism that loops time.
- 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_69c008593a44819081a07ae0efe6c574 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0334fcf6481908e8e74105de9d49b |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:59 p.m.