Triple
T25202796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Forks Formation |
E631164
|
entity |
| Predicate | presentInStateOrProvince |
P96807
|
FINISHED |
| Object | Montana |
—
|
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: Montana | Statement: [Three Forks Formation, presentInStateOrProvince, Montana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentInStateOrProvince Context triple: [Three Forks Formation, presentInStateOrProvince, Montana]
-
A.
isInProvince
Indicates that one entity (typically a place or city) is located within the administrative boundaries of a specified province.
-
B.
includesStateOrProvince
Indicates that one entity geographically contains or encompasses a specific state or province within its boundaries.
-
C.
locatedInStateOrRegion
chosen
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
D.
hasProvinceOrRegion
Indicates that one entity includes, is associated with, or is located within a specific province or region as an administrative or geographic subdivision.
-
E.
associatedProvinceOrState
Indicates that one entity is linked or related to a specific province or state as its relevant administrative region.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f474b904f48190be6513788f89c6a9 |
completed | May 1, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:51 p.m.