Triple
T8014386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monitor Range |
E186573
|
entity |
| Predicate | hasWildernessCharacter |
P80571
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Monitor Range, hasWildernessCharacter, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWildernessCharacter Context triple: [Monitor Range, hasWildernessCharacter, yes]
-
A.
hasWildernessArea
Indicates that one entity possesses, contains, or is associated with a designated wilderness area.
-
B.
containsWildernessArea
Indicates that one entity geographically includes or encompasses a designated wilderness area within its boundaries.
-
C.
containsWildSpecies
Indicates that one entity includes, houses, or encompasses wild (non-domesticated) species within its scope or boundaries.
-
D.
hasWildlifeAccess
Indicates that an entity has the ability, permission, or physical means to reach or interact with wildlife or wildlife habitats.
-
E.
hasNearbyWildernessArea
Indicates that a wilderness area is located within a close geographic proximity to the referenced place or entity.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3df0f4bc8190ae87586972018085 |
completed | March 31, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:19 p.m.