Triple
T7881552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northeast Entrance near Cooke City |
E182989
|
entity |
| Predicate | nearWildlifeArea |
P34896
|
FINISHED |
| Object | prime habitat for elk |
—
|
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: prime habitat for elk | Statement: [Northeast Entrance near Cooke City, nearWildlifeArea, prime habitat for elk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearWildlifeArea Context triple: [Northeast Entrance near Cooke City, nearWildlifeArea, prime habitat for elk]
-
A.
hasNearbyWildernessArea
Indicates that a wilderness area is located within a close geographic proximity to the referenced place or entity.
-
B.
associatedWithWildlifeArea
Indicates that an entity has a connection, involvement, or linkage with a designated wildlife area.
-
C.
hasNearbyNatureReserve
Indicates that one place or entity is located close to a designated nature reserve.
-
D.
hasNearbyWildlife
chosen
Indicates that there is wildlife located close to or in the immediate vicinity of the referenced entity.
-
E.
nearNationalForest
Indicates that one entity is located close to, but not necessarily inside, a designated national forest area.
- 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_69ca828af6e48190a06ee7010d8f0e64 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39c14a188190a225ca3c7e515b0c |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:58 p.m.