Triple
T2265063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nez Perce War |
E50124
|
entity |
| Predicate | distanceCovered |
P16230
|
FINISHED |
| Object | approximately 1,170 miles |
—
|
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: approximately 1,170 miles | Statement: [Nez Perce War, distanceCovered, approximately 1,170 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceCovered Context triple: [Nez Perce War, distanceCovered, approximately 1,170 miles]
-
A.
distanceTraveled
chosen
Indicates the total length of the path an entity has moved over a period of time or between two points.
-
B.
distance
Indicates the spatial separation or length between two points, objects, or locations.
-
C.
movementComponentsCovered
Indicates that the movement or motion of an entity is fully accounted for or represented by a specified set of component movements.
-
D.
flightDistance
Indicates the measured distance covered by a flight between its origin and destination.
-
E.
lengthInKm
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
- 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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc2ea65288190bc8644a07a11dfa9 |
completed | March 7, 2026, 6:17 a.m. |
| PD | Predicate disambiguation | batch_69abbdb592588190ac1ef5e8c54575b1 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.