Triple
T6019855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bears Ears National Monument |
E134036
|
entity |
| Predicate | reducedArea |
P19675
|
FINISHED |
| Object | approximately 201,876 acres |
—
|
LITERAL FINISHED |
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: approximately 201,876 acres | Statement: [Bears Ears National Monument, reducedArea, approximately 201,876 acres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reducedArea Context triple: [Bears Ears National Monument, reducedArea, approximately 201,876 acres]
-
A.
reducedTerritoryOf
chosen
Indicates that one entity has caused a decrease in the size or extent of another entity's territory or area of control.
-
B.
coveredArea
Indicates that one entity occupies or extends over a specific spatial region or surface area associated with another entity.
-
C.
reducedCapacity
Indicates that an entity is functioning with less than its normal or full capacity, ability, or effectiveness.
-
D.
representedArea
Indicates that one entity serves as a representation or depiction of a particular area or region.
-
E.
designedArea
Indicates that an area has been intentionally planned, shaped, or configured according to a specific design or purpose.
- 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_69c008742a5c8190b9cb9c2787a3d8b3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f86efec8190bc357dddf6ebb4a9 |
completed | March 22, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:07 p.m.