Triple
T36702253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Trail region |
E906260
|
entity |
| Predicate | traversesPresentDay |
P188148
|
FINISHED |
| Object | Missouri |
—
|
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: Missouri | Statement: [Oregon Trail region, traversesPresentDay, Missouri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traversesPresentDay Context triple: [Oregon Trail region, traversesPresentDay, Missouri]
-
A.
flowsThroughPresentDay
Indicates that something such as a river or current passes through or traverses the area of a place as it exists in the present day.
-
B.
partOfPresentDay
Indicates that one entity is a component, region, or subset of what constitutes the other entity in its current, modern-day form.
-
C.
landedInPresentDay
Indicates that an entity arrived or came to rest in a location corresponding to where that place exists in the present day.
-
D.
usesTimeTravelFor
Indicates a relationship where an entity employs time travel as a means or method to achieve, affect, or interact with another entity or objective.
-
E.
timeTravelTo
Indicates traveling from one point in time to another, typically different, point in time.
- F. None of above. chosen
Provenance (4 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:12 p.m.