Triple
T29981354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Tahoma Peak |
E761599
|
entity |
| Predicate | fallsUnderManagementOf |
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: [Little Tahoma Peak, fallsUnderManagementOf, U.S. National Park Service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fallsUnderManagementOf Context triple: [Little Tahoma Peak, fallsUnderManagementOf, U.S. National Park Service]
-
A.
isUnderAdministrationOf
chosen
Indicates that one entity is managed, governed, or overseen by another authority or administrative body.
-
B.
endedUnderAdministration
Indicates that an entity’s existence, operation, or status concluded while it was under the control or management of a particular administrative authority.
-
C.
isUnderControlOf
Indicates that one entity is subject to the authority, direction, or governance of another entity.
-
D.
laterManagedBy
Indicates that an entity was, at a subsequent time, managed or overseen by another entity.
-
E.
boundaryManagedBy
Indicates that the defined boundary is overseen, controlled, or administered by a specific managing 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f678d92c4c8190854b1d388e659b7a |
completed | May 2, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:35 p.m.