Triple
T33571479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Nebraska |
E859911
|
entity |
| Predicate | traversedHistoricallyBy |
P12633
|
FINISHED |
| Object | overland trails |
—
|
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: overland trails | Statement: [Central Nebraska, traversedHistoricallyBy, overland trails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traversedHistoricallyBy Context triple: [Central Nebraska, traversedHistoricallyBy, overland trails]
-
A.
historicallyExtendedBy
Indicates that something has been continued, expanded, or carried forward over time by another, later entity or development.
-
B.
hasHistoricalRoute
chosen
Indicates that an entity possesses or is associated with a route that has historical significance or origin.
-
C.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
D.
hasHistoricalArc
Indicates that something unfolds over time in a way that forms a coherent, meaningful historical development or narrative.
-
E.
hasTransportHistoryAs
Indicates that an entity has a record or log of being transported, characterized or classified in a specific way.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:40 a.m.