Triple
T29129073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Fork Smith River |
E738318
|
entity |
| Predicate | subjectToManagementBy |
P149548
|
FINISHED |
| Object | U.S. Forest 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. Forest Service | Statement: [South Fork Smith River, subjectToManagementBy, U.S. Forest Service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectToManagementBy Context triple: [South Fork Smith River, subjectToManagementBy, U.S. Forest 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.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
D.
boundaryManagedBy
Indicates that the defined boundary is overseen, controlled, or administered by a specific managing entity.
-
E.
sectorManaged
Indicates that one entity is responsible for administering, overseeing, or directing the operations of a particular sector.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 28, 2026, 11:30 a.m.