Triple
T14723445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tony Conigliaro Award |
E345872
|
entity |
| Predicate | typeOfAdversity |
P41218
|
FINISHED |
| Object | injury |
—
|
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: injury | Statement: [Tony Conigliaro Award, typeOfAdversity, injury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAdversity Context triple: [Tony Conigliaro Award, typeOfAdversity, injury]
-
A.
seeksToOvercome
Indicates an intentional effort by one entity to defeat, surpass, or remove an obstacle, limitation, or opposing force associated with another entity or condition.
-
B.
hardship
chosen
Indicates that an entity is experiencing or causing significant difficulty, suffering, or adverse conditions.
-
C.
typeOfBravery
Indicates a specific kind or category of bravery that characterizes an entity’s courageous behavior or action.
-
D.
typeOfResistance
Indicates the kind or category of resistance that characterizes how an entity opposes, impedes, or withstands another entity or influence.
-
E.
associatedWithStruggle
Indicates a relationship in which an entity is connected to, involved in, or characterized by a particular struggle, conflict, or hardship.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec25e9a14819081fa06fc601f295d |
completed | April 14, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.