Triple
T20497230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gideon Prewett |
E502905
|
entity |
| Predicate | bravery |
P83830
|
FINISHED |
| Object | described as very brave |
—
|
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: described as very brave | Statement: [Gideon Prewett, bravery, described as very brave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bravery Context triple: [Gideon Prewett, bravery, described as very brave]
-
A.
typeOfBravery
Indicates a specific kind or category of bravery that characterizes an entity’s courageous behavior or action.
-
B.
moralCourage
Indicates the quality of acting ethically or standing up for moral principles despite facing fear, risk, or social pressure.
-
C.
strength
Indicates the degree of power, intensity, or effectiveness with which an entity can act on, influence, or withstand another entity or force.
-
D.
describesGallantryOf
chosen
Indicates a relationship where one entity characterizes, explains, or details the gallant or brave behavior of another entity.
-
E.
inspiration
Indicates that one entity serves as a motivating or creative influence that stimulates ideas, actions, or feelings in 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_69e0b4b0373881909dd3e9387f82eab4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cbefe4c819098af5bfd4d92341d |
completed | April 20, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:35 a.m.