Triple
T29137051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book Three: Fire |
E738534
|
entity |
| Predicate | featuresBendingDiscipline |
P119495
|
FINISHED |
| Object | firebending |
—
|
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: firebending | Statement: [Book Three: Fire, featuresBendingDiscipline, firebending]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresBendingDiscipline Context triple: [Book Three: Fire, featuresBendingDiscipline, firebending]
-
A.
featuredDiscipline
Indicates that one discipline is highlighted or given special prominence in relation to another entity or context.
-
B.
bendingSubskill
chosen
Indicates a specific skill or technique that forms part of the broader ability to bend or flex something.
-
C.
offersDiscipline
Indicates that one entity provides or makes available a particular field of study, training, or area of specialization to another entity.
-
D.
strokeDiscipline
Indicates the specific swimming stroke or discipline associated with a swimming-related event, performance, or activity.
-
E.
typeDiscipline
Indicates that an entity is associated with, categorized under, or characterized by a particular discipline or field of study.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
Created at: April 28, 2026, 11:35 a.m.