Triple
T24872558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnny Cade |
E622473
|
entity |
| Predicate | actOfHeroism |
P36130
|
FINISHED |
| Object | saving children from 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: saving children from fire | Statement: [Johnny Cade, actOfHeroism, saving children from fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actOfHeroism Context triple: [Johnny Cade, actOfHeroism, saving children from fire]
-
A.
describesGallantryOf
Indicates a relationship where one entity characterizes, explains, or details the gallant or brave behavior of another entity.
-
B.
sacrificedLifeToSaveOthers
Indicates that an entity willingly gave up their own life in order to protect or rescue other entities.
-
C.
typeOfBravery
Indicates a specific kind or category of bravery that characterizes an entity’s courageous behavior or action.
-
D.
notableDeed
chosen
Indicates that an entity is recognized for performing a significant or noteworthy action or achievement.
-
E.
heroPerformsFor
Indicates that a hero carries out an action or performance for the benefit, entertainment, or service of another entity.
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:23 a.m.