Triple
T28791711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redwood Grove Loop Trail |
E726971
|
entity |
| Predicate | primaryFloraCommonName |
P83264
|
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 Grove Loop Trail, primaryFloraCommonName, coast redwood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFloraCommonName Context triple: [Redwood Grove Loop Trail, primaryFloraCommonName, coast redwood]
-
A.
taxonCommonName
Indicates that a taxonomic entity is associated with a common (vernacular) name used in everyday language.
-
B.
associatedFlora
chosen
Indicates a relationship where specific plants or vegetation are characteristically linked to, occur with, or are commonly found in association with a given entity or environment.
-
C.
plantName
Indicates that the associated value is the name or designated label of a plant.
-
D.
describedTaxonCommonName
Indicates that a taxon is being described or referenced using its common (vernacular) name rather than its scientific name.
-
E.
dominantTreeCommonName
Indicates the common (non-scientific) name of the tree species that is dominant in a given area or ecological context.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a007aa8d3a481908543f9b5d562a90c |
completed | May 10, 2026, 12:31 p.m. |
| PD | Predicate disambiguation | batch_6a007a44996481908688ccfdbc56511d |
completed | May 10, 2026, 12:29 p.m. |
Created at: April 28, 2026, 6:23 a.m.