Triple
T24863174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herb Elliott |
E622207
|
entity |
| Predicate | dominatedDiscipline |
P158126
|
FINISHED |
| Object | mile run |
—
|
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: mile run | Statement: [Herb Elliott, dominatedDiscipline, mile run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominatedDiscipline Context triple: [Herb Elliott, dominatedDiscipline, mile run]
-
A.
dominatedDiscipline
chosen
Indicates that one entity exerted controlling power or authority over another within a specific discipline or field.
-
B.
attractsDiscipline
Indicates a relationship where one entity draws or brings about discipline, order, or self-control in another entity.
-
C.
governingDiscipline
Indicates that one discipline or field provides the primary rules, principles, or framework that regulate or guide another activity, domain, or practice.
-
D.
dominatedBy
Indicates that one entity is under the control, influence, or overpowering authority of another entity.
-
E.
featuredDiscipline
Indicates that one discipline is highlighted or given special prominence in relation to another entity or context.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 5:22 a.m.