Triple
T26218986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camel’s Hump State Forest |
E655711
|
entity |
| Predicate | managesLandscapeAround |
P110999
|
FINISHED |
| Object | Camel’s Hump |
—
|
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: Camel’s Hump | Statement: [Camel’s Hump State Forest, managesLandscapeAround, Camel’s Hump]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesLandscapeAround Context triple: [Camel’s Hump State Forest, managesLandscapeAround, Camel’s Hump]
-
A.
landscapeManagement
chosen
Indicates the planning, implementation, and maintenance of actions that shape, conserve, or restore the physical and ecological characteristics of a landscape.
-
B.
landscapeRole
Indicates the functional or symbolic role that an entity plays within a particular landscape or environmental setting.
-
C.
landscapeElement
Indicates that one entity functions as a landscape-related feature or component in relation to another entity.
-
D.
gardenManagedBy
Indicates that a garden is overseen, maintained, or administered by a particular person, group, or organization.
-
E.
hasLandscaping
Indicates that an entity possesses or is associated with designed outdoor grounds or landscape features.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 26, 2026, 8:55 p.m.