Triple
T7710805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redwood Canyon |
E174744
|
entity |
| Predicate | hasMainTreeSpeciesCommonName |
P966
|
FINISHED |
| Object | coast redwood |
—
|
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: coast redwood | Statement: [Redwood Canyon, hasMainTreeSpeciesCommonName, coast redwood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainTreeSpeciesCommonName Context triple: [Redwood Canyon, hasMainTreeSpeciesCommonName, coast redwood]
-
A.
notableTreeSpecies
chosen
Indicates that the subject place or area is known for, or characterized by, the specified tree species.
-
B.
hasSurroundingTreeCommonName
Indicates that an entity is associated with a surrounding tree identified by its common (vernacular) name.
-
C.
treeHabit
Indicates the growth form or structural habit characteristic of a tree, such as its typical shape, branching pattern, or overall stature.
-
D.
includesSpeciesCommonName
Indicates that an entity contains or specifies the common (vernacular) name of a species.
-
E.
hasForestType
Indicates that an area or location is characterized by a specific type or classification of forest.
- 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_69c6995b3e8c8190833108f883d5f53c |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:04 p.m.