Triple
T17466403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benguet pine |
E425287
|
entity |
| Predicate | fireEcologyRole |
P127559
|
FINISHED |
| Object | fire-adapted species |
—
|
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: fire-adapted species | Statement: [Benguet pine, fireEcologyRole, fire-adapted species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fireEcologyRole Context triple: [Benguet pine, fireEcologyRole, fire-adapted species]
-
A.
wildfireRisk
Indicates the likelihood or potential severity of wildfires occurring in a given area or under specific conditions.
-
B.
hasFireRegime
Indicates that an area or ecosystem is characterized by a particular pattern, frequency, and intensity of fires over time.
-
C.
fireType
Indicates that one entity has a specific classification or category related to fire (e.g., type, kind, or nature of fire).
-
D.
fireSymbolizes
Indicates that the concept or element of fire is used to represent, signify, or stand for another idea, quality, or meaning in a symbolic way.
-
E.
methodOfKillingWildfire
Indicates the method or technique used to kill or extinguish a wildfire.
- F. None of above. chosen
Provenance (4 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451a7e2a481908c32defa3401f848 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:47 a.m.