Triple
T21161820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian Ridgeback |
E521460
|
entity |
| Predicate | fireBreathingAbility |
P112379
|
FINISHED |
| Object | can breathe fire at a young age |
—
|
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: can breathe fire at a young age | Statement: [Norwegian Ridgeback, fireBreathingAbility, can breathe fire at a young age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fireBreathingAbility Context triple: [Norwegian Ridgeback, fireBreathingAbility, can breathe fire at a young age]
-
A.
canControlFlames
chosen
Indicates the ability of one entity to generate, manipulate, or otherwise exert control over fire or flames.
-
B.
fireUse
Indicates the use or application of fire by one entity on, with, or for another entity or object.
-
C.
fireEffect
Indicates that one entity produces, causes, or is associated with a fire-related impact or consequence on another entity.
-
D.
burnCapability
Indicates that an entity has the ability or potential to burn, ignite, or cause combustion under certain conditions.
-
E.
fireType
Indicates that one entity has a specific classification or category related to fire (e.g., type, kind, or nature of fire).
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72530e3388190a170c5a2a19dadfc |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:59 p.m.