Triple
T35937575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebraska |
E1039346
|
entity |
| Predicate | historicalTrail |
P29483
|
FINISHED |
| Object | Oregon Trail |
—
|
NE NERFINISHED |
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: Oregon Trail | Statement: [Nebraska, historicalTrail, Oregon Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalTrail Context triple: [Nebraska, historicalTrail, Oregon Trail]
-
A.
historicRoute
chosen
Indicates that a route has historical significance, typically due to its age, past usage, or role in notable events.
-
B.
historicRouteType
Indicates the specific kind or classification of a route in terms of its historical significance or use.
-
C.
historicalExploration
Indicates that an entity has engaged in or is associated with the act of exploring or investigating something in the past.
-
D.
historicalRouteVia
Indicates that a historical route or path passed through or was connected by a particular intermediate location or segment.
-
E.
historicalTraction
Indicates that the subject has demonstrated sustained relevance, influence, or effectiveness over a significant period of time.
- 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_69f76e24bbd0819096b837d35371639a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00ccadb6908190ab810a7c05315fa8 |
completed | May 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_6a00cc0f86b88190a0d2c43618558f86 |
completed | May 10, 2026, 6:18 p.m. |
Created at: May 3, 2026, 4:07 p.m.