Triple
T9980277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnny Smith |
E196432
|
entity |
| Predicate | gainsPowersAfter |
P89517
|
FINISHED |
| Object | waking from coma |
—
|
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: waking from coma | Statement: [Johnny Smith, gainsPowersAfter, waking from coma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainsPowersAfter Context triple: [Johnny Smith, gainsPowersAfter, waking from coma]
-
A.
gainedPowerAfter
chosen
Indicates that one entity acquired power, authority, or influence subsequent to an event, condition, or action involving another entity.
-
B.
enhancesPowersOf
Indicates that one entity increases, amplifies, or strengthens the abilities or powers of another entity.
-
C.
methodOfGainingPower
Indicates the way or process through which an entity acquires or increases power.
-
D.
regainedPowerIn
Indicates that an entity has recovered or reestablished its previous level of power, control, or authority within a specified context or domain.
-
E.
regainedPowerAgainIn
Indicates that an entity, having previously lost power, has once more returned to a position of power or control within a specified context or location.
- 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_69ca82efbce081908179b4b9c65096eb |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb8b9aca881908a9b5dfd7e0de4ba |
completed | April 2, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:49 p.m.