Triple
T30836458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Alamitos Race Course |
E785378
|
entity |
| Predicate | hasNotableDistance |
P78943
|
FINISHED |
| Object | 440 yards |
—
|
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: 440 yards | Statement: [Los Alamitos Race Course, hasNotableDistance, 440 yards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableDistance Context triple: [Los Alamitos Race Course, hasNotableDistance, 440 yards]
-
A.
hasUncertainDistance
Indicates that the distance between two entities is not known precisely or cannot be determined with certainty.
-
B.
hasNotableNumber
chosen
Indicates that an entity is associated with a specific number that is considered significant, distinctive, or noteworthy in some context.
-
C.
hasDistanceElement
Indicates that one entity includes or is associated with a component that specifies a distance value or measurement.
-
D.
hasDistanceCategory
Indicates that one entity is associated with a qualitative or categorical classification of its distance relative to another entity or reference point.
-
E.
isDistant
Indicates that one entity is far away or separated by a large distance from another entity.
- 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_69f224b73d8c81908129383bfb397c87 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a005e8a2f7c819085bfc6f04b866d87 |
completed | May 10, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_6a005de82ef08190a015b385d1d3443c |
completed | May 10, 2026, 10:28 a.m. |
Created at: April 29, 2026, 8:45 p.m.