Triple
T8254280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wheeler Peak Bristlecone Pine Grove |
E193031
|
entity |
| Predicate | treeWoodProperty |
P1357
|
FINISHED |
| Object | dense, resinous wood |
—
|
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: dense, resinous wood | Statement: [Wheeler Peak Bristlecone Pine Grove, treeWoodProperty, dense, resinous wood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treeWoodProperty Context triple: [Wheeler Peak Bristlecone Pine Grove, treeWoodProperty, dense, resinous wood]
-
A.
woodProperty
chosen
Indicates that one entity specifies or characterizes a property or attribute of wood associated with another entity.
-
B.
treeUse
Indicates the way in which a tree is utilized or purposed within a given context.
-
C.
lakeProperty
Indicates that a property is located on, adjacent to, or otherwise directly associated with a lake.
-
D.
architectureProperty
Indicates that a specified architectural characteristic or feature is attributed to, or associated with, an entity.
-
E.
houseTraitAssociation
Indicates an associative relationship between a house and a particular trait or characteristic attributed to it.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78f8eccc8190b43204bf2f8defc1 |
completed | March 31, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.