Triple
T33598194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Private |
E860634
|
entity |
| Predicate | braveryType |
P27803
|
FINISHED |
| Object | acts bravely despite fear |
—
|
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: acts bravely despite fear | Statement: [Private, braveryType, acts bravely despite fear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: braveryType Context triple: [Private, braveryType, acts bravely despite fear]
-
A.
typeOfBravery
chosen
Indicates a specific kind or category of bravery that characterizes an entity’s courageous behavior or action.
-
B.
isBrave
Indicates that an entity consistently faces danger, fear, or adversity with courage and determination.
-
C.
heroicAction
Indicates that an entity performs a brave, selfless, or morally admirable action, often involving risk or sacrifice for the benefit of others.
-
D.
typeOfResistance
Indicates the kind or category of resistance that characterizes how an entity opposes, impedes, or withstands another entity or influence.
-
E.
describesGallantryOf
Indicates a relationship where one entity characterizes, explains, or details the gallant or brave behavior 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f7a6486c8190811ecf3ea5fedba5 |
completed | May 3, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:41 a.m.