Triple
T32316835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reynolds Mountain |
E825658
|
entity |
| Predicate | isWithinManagementOf |
P149548
|
FINISHED |
| Object | U.S. National Park Service |
—
|
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: U.S. National Park Service | Statement: [Reynolds Mountain, isWithinManagementOf, U.S. National Park Service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWithinManagementOf Context triple: [Reynolds Mountain, isWithinManagementOf, U.S. National Park Service]
-
A.
isManagedThrough
Indicates that one entity is administered, controlled, or operated by means of another entity, typically specifying the mechanism, channel, or system used for its management.
-
B.
isUnderAdministrationOf
chosen
Indicates that one entity is managed, governed, or overseen by another authority or administrative body.
-
C.
hasManagementArea
Indicates that one entity is responsible for managing, overseeing, or administering a specified area or region.
-
D.
isUnderControlOf
Indicates that one entity is subject to the authority, direction, or governance of another entity.
-
E.
hasManagement
Indicates that one entity exercises managerial authority or oversight over another entity.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bdbc092c81908d93b4c4a4899cde |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:46 a.m.