Triple
T16428718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D.K. Metcalf |
E399013
|
entity |
| Predicate | combineEvent |
P122745
|
FINISHED |
| Object | 40-yard dash |
—
|
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: 40-yard dash | Statement: [D.K. Metcalf, combineEvent, 40-yard dash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combineEvent Context triple: [D.K. Metcalf, combineEvent, 40-yard dash]
-
A.
unionEvent
Indicates an event in which two or more entities are joined or combined into a single unified whole.
-
B.
combinedIn
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
C.
includesEvents
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
-
D.
coordinateEvent
Indicates overseeing and organizing the planning, logistics, and execution of an event in collaboration with involved parties.
-
E.
hasCompanionEvent
Indicates that one event is associated with another event that occurs alongside it as a related or accompanying occurrence.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328fd49708190abb5065fa430eff1 |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:09 a.m.