Triple
T4036514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoh Rain Forest |
E83839
|
entity |
| Predicate | managementBody |
P29724
|
FINISHED |
| Object | Olympic National Park administration |
—
|
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: Olympic National Park administration | Statement: [Hoh Rain Forest, managementBody, Olympic National Park administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managementBody Context triple: [Hoh Rain Forest, managementBody, Olympic National Park administration]
-
A.
managementIncludes
Indicates that a management entity encompasses, oversees, or has responsibility for the included entity or entities.
-
B.
manager
Indicates that one entity holds a supervisory or administrative role with authority and responsibility over another entity.
-
C.
governingBodyUser
Indicates that a user acts as a governing or decision-making authority for a particular entity or organization.
-
D.
managingCenter
Indicates that one entity serves as the administrative or coordinating center responsible for managing another entity or activity.
-
E.
managedIn
chosen
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb349e648190b9f227df4cd76fa0 |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef8fe440c819093a7fa22c4ff3f1a |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:36 p.m.