Triple
T30744245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agate Basin complex |
E782773
|
entity |
| Predicate | foundInStateOrProvince |
P96807
|
FINISHED |
| Object | Wyoming |
—
|
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: Wyoming | Statement: [Agate Basin complex, foundInStateOrProvince, Wyoming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInStateOrProvince Context triple: [Agate Basin complex, foundInStateOrProvince, Wyoming]
-
A.
locatedInStateOrRegion
chosen
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
B.
discoveredInProvince
Indicates that something was discovered within the geographical boundaries of a particular province.
-
C.
associatedProvinceOrState
Indicates that one entity is linked or related to a specific province or state as its relevant administrative region.
-
D.
isProvinceOf
Indicates that one region holds the administrative status of a province within, and is governed as a subnational division of, another political entity.
-
E.
foundInRegion
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: April 29, 2026, 8:38 p.m.