Triple
T25797214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Betatakin |
E649719
|
entity |
| Predicate | onPlateau |
P159280
|
FINISHED |
| Object | Colorado Plateau |
—
|
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: Colorado Plateau | Statement: [Betatakin, onPlateau, Colorado Plateau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onPlateau Context triple: [Betatakin, onPlateau, Colorado Plateau]
-
A.
hasPlateaus
Indicates that something possesses or contains one or more plateau-like flat elevated areas.
-
B.
hasPlateauSize
Indicates that an entity possesses or is characterized by a specific plateau size, typically referring to the extent or magnitude of a flat or stable region.
-
C.
onPlate
Indicates that one entity is physically resting atop and supported by the surface of a plate.
-
D.
hasMajorPlateau
Indicates that an entity possesses or includes a primary, extensive plateau as a significant geographic or structural feature.
-
E.
reachedPeak
Indicates that an entity has attained its highest or maximum level, value, or performance within a given context or timeframe.
- F. None of above. chosen
Provenance (4 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5ffc8635881909f3e05e3903f8d8c |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 6:32 a.m.