Triple
T6769037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miracle Mile (1954 race) |
E154996
|
entity |
| Predicate | bothRunnersSubFour |
P73170
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Miracle Mile (1954 race), bothRunnersSubFour, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bothRunnersSubFour Context triple: [Miracle Mile (1954 race), bothRunnersSubFour, true]
-
A.
baseRunners
Indicates that certain players are currently occupying one or more bases as runners in a baseball play or game situation.
-
B.
frontRunnerAtStart
Indicates that an entity is the leading competitor or in first position at the beginning of an event or process.
-
C.
hasRunSub10Seconds100m
Indicates that the subject has completed a 100-meter sprint in under 10 seconds.
-
D.
runsTheLengthOf
Indicates that one entity extends continuously alongside or across the full distance of another entity.
-
E.
eventualFrontRunner
Indicates that an entity is expected or predicted to become the leading or most successful one among a set of competitors in the future.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d232d1f08190bc30c0f24f28c475 |
completed | March 27, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1d5f1908190989efc8a2d18c965 |
completed | March 27, 2026, 6:52 p.m. |
Created at: March 27, 2026, 2:12 p.m.