Triple
T71501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Douglas fir |
E1430
|
entity |
| Predicate | fireEcology |
P1980
|
FINISHED |
| Object | moderately fire-resistant bark in mature trees |
—
|
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: moderately fire-resistant bark in mature trees | Statement: [Douglas fir, fireEcology, moderately fire-resistant bark in mature trees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fireEcology Context triple: [Douglas fir, fireEcology, moderately fire-resistant bark in mature trees]
-
A.
seedDispersal
Indicates the process by which seeds are transported away from the parent organism to new locations, often via wind, water, or animals.
-
B.
fireAdaptation
chosen
Indicates that an entity possesses traits or mechanisms that enable it to survive, reproduce, or otherwise benefit in environments where fire occurs.
-
C.
vegetation
Indicates that an area or object is covered with, contains, or is characterized by plant life.
-
D.
biome
Indicates the type of ecological environment or habitat in which an entity naturally exists or is situated.
-
E.
vegetationType
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a24f6997c081908b202f937eb2b14f |
completed | Feb. 28, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69a24eab7f408190a8275cb82474f575 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.