Triple
T4528884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri River Basin |
E106245
|
entity |
| Predicate | majorCityInBasin |
P9892
|
FINISHED |
| Object | Billings |
E45126
|
NE 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: Billings | Statement: [Missouri River Basin, majorCityInBasin, Billings]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Billings Context triple: [Missouri River Basin, majorCityInBasin, Billings]
-
A.
Billings
chosen
Billings is the largest city in the U.S. state of Montana and a major economic and cultural hub for the surrounding Mountain States region.
-
B.
Billings
Billings is a small rural municipality located on Manitoulin Island in Ontario, Canada.
-
C.
Billings
Billings is the middle name of Henry Billings Brown, an American jurist who served as an Associate Justice of the U.S. Supreme Court in the late 19th and early 20th centuries.
-
D.
Missoula
Missoula is a vibrant city in western Montana known for its university, outdoor recreation, and cultural scene.
-
E.
Rapid City
Rapid City is a city in western South Dakota known as a gateway to the Black Hills and nearby Mount Rushmore.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd5779593081908593537b9239e01b |
completed | March 20, 2026, 2:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bda45eadd0819093429e14c88a161d |
completed | March 20, 2026, 7:47 p.m. |
Created at: March 20, 2026, 1:03 p.m.