Triple
T36654146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curtis Formation |
E904943
|
entity |
| Predicate | isPartOfBasin |
P123912
|
FINISHED |
| Object | Cordilleran foreland region |
—
|
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: Cordilleran foreland region | Statement: [Curtis Formation, isPartOfBasin, Cordilleran foreland region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfBasin Context triple: [Curtis Formation, isPartOfBasin, Cordilleran foreland region]
-
A.
locatedInBasin
Indicates that one geographical or hydrological feature lies within the drainage or catchment area of a specified basin.
-
B.
basinPartOf
Indicates that one basin is a component or subdivision of a larger basin or basin system.
-
C.
isPrincipalBasinOf
Indicates that one basin serves as the main or primary drainage basin associated with another geographic or hydrologic feature.
-
D.
basinFor
Indicates that something serves as a basin or receptacle specifically intended for collecting, holding, or draining another entity.
-
E.
isPartOfBasinFill
chosen
Indicates that a geological unit or deposit belongs to, and was formed as part of, the sedimentary fill within a structural or depositional basin.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
Created at: May 3, 2026, 4:11 p.m.