Triple
T35637123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colin’s Crest Award |
E1029750
|
entity |
| Predicate | recordDistanceYear |
P102987
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Colin’s Crest Award, recordDistanceYear, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordDistanceYear Context triple: [Colin’s Crest Award, recordDistanceYear, 2016]
-
A.
trackRecordDistance
Indicates that one entity holds the record for the greatest distance achieved in a particular tracking or performance context.
-
B.
distanceRecord
Indicates that a specific distance value has been measured, recorded, or maintained between two entities or locations.
-
C.
hourRecordDistance
Indicates that one entity holds or represents the record for the greatest distance covered within a one-hour time period relative to another entity or context.
-
D.
lastRecordedIndividualYear
Indicates the calendar year in which the last known individual of a species or population was recorded.
-
E.
yearOfWorldRecord
chosen
Indicates the specific year in which a particular world record was set or achieved.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.