Triple
T14318357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adenostoma fasciculatum |
E355015
|
entity |
| Predicate | fireResponse |
P113955
|
FINISHED |
| Object | resprouts from root crown after fire |
—
|
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: resprouts from root crown after fire | Statement: [Adenostoma fasciculatum, fireResponse, resprouts from root crown after fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fireResponse Context triple: [Adenostoma fasciculatum, fireResponse, resprouts from root crown after fire]
-
A.
fireOccurred
Indicates that a fire event took place at a specific time and/or location.
-
B.
fireServiceBy
Indicates that a fire protection or firefighting service is provided, operated, or carried out by a specified agent or organization.
-
C.
fireProblemSince
Indicates that a fire-related problem has been occurring or has been present since a specific point in time.
-
D.
firefightingResponse
Indicates the action of responding to and attempting to control or extinguish a fire or related emergency.
-
E.
fires
Indicates that an agent initiates the discharge or ignition of something, such as a weapon, engine, or explosive device, causing it to operate or go off.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de883a93548190ac671b001d15d0bd |
completed | April 14, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e9ded24819099200349cf80e068 |
completed | April 14, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:13 a.m.