Triple
T30283670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon pioneers |
E770172
|
entity |
| Predicate | usedMigrationRoute |
P22721
|
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: [Oregon pioneers, usedMigrationRoute, Oregon Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedMigrationRoute Context triple: [Oregon pioneers, usedMigrationRoute, Oregon Trail]
-
A.
usedInMigration
Indicates that something serves as a component, tool, or resource within a migration process or workflow.
-
B.
migrationFrom
Indicates that an entity has moved, originated, or been transferred away from a specified source location or context.
-
C.
supportsMigrationOf
Indicates that one entity enables, facilitates, or is compatible with the migration or transfer of another entity from one environment, system, or context to another.
-
D.
enabledMigrationOf
Indicates that one entity made it possible for another entity to move, transfer, or transition from one state, location, or system to another.
-
E.
associatedWithMigration
chosen
Indicates a relationship or connection between entities that is linked to, results from, or occurs in the context of migration.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68106a8ac8190ab775d61ae360c56 |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:45 p.m.