Triple
T37452270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sundance, Wyoming |
E930699
|
entity |
| Predicate | hasNearbyGeologicalUnit |
P155643
|
FINISHED |
| Object | Sundance Formation |
—
|
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: Sundance Formation | Statement: [Sundance, Wyoming, hasNearbyGeologicalUnit, Sundance Formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyGeologicalUnit Context triple: [Sundance, Wyoming, hasNearbyGeologicalUnit, Sundance Formation]
-
A.
hasGeologicalUnit
Indicates that an entity is associated with or contains a specific geological unit, such as a rock layer, formation, or stratigraphic unit.
-
B.
geologicUnitOf
Indicates that one entity is a geologic unit to which the other entity belongs or with which it is associated.
-
C.
nearGeologicalSite
Indicates that one entity is located in close physical proximity to a geological site or feature.
-
D.
hasNearbyGeographicalArea
Indicates that one geographical area is located in close spatial proximity to another geographical area.
-
E.
hasNearbyRockFormation
chosen
Indicates that one entity is located close to or adjacent to a rock formation.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00a22e32f481909b6006c5b1cdefd3 |
completed | May 10, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_6a00a1bd9c908190b4aa17a61f48126f |
completed | May 10, 2026, 3:18 p.m. |
Created at: May 3, 2026, 4:17 p.m.