Triple
T5211036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri River |
E117632
|
entity |
| Predicate | explorationPeriod |
P26767
|
FINISHED |
| Object | 1804–1806 |
—
|
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: 1804–1806 | Statement: [Missouri River, explorationPeriod, 1804–1806]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explorationPeriod Context triple: [Missouri River, explorationPeriod, 1804–1806]
-
A.
hasDiscoveryPeriod
chosen
Indicates the time span during which a particular discovery was made or recognized.
-
B.
approximateIntroductionPeriod
Indicates the approximate time period during which an entity was first introduced or came into use.
-
C.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
D.
launchPeriod
Indicates the time span during which a launch or deployment activity occurs or is valid.
-
E.
explorationStatus
Indicates the current state or phase of an exploration process or activity between entities.
- 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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a7166848190805152142e184529 |
completed | March 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.