Triple
T27851953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turbulence |
E703976
|
entity |
| Predicate | featuresProtagonistAbility |
P85648
|
FINISHED |
| Object | Aman Sen has power over information networks |
—
|
NE NERFINISHED |
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: Aman Sen has power over information networks | Statement: [Turbulence, featuresProtagonistAbility, Aman Sen has power over information networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresProtagonistAbility Context triple: [Turbulence, featuresProtagonistAbility, Aman Sen has power over information networks]
-
A.
hasProtagonistAbility
chosen
Indicates that a protagonist possesses a specific ability, power, or special skill.
-
B.
featuresSpecialAbility
Indicates that an entity possesses or is characterized by a particular special ability.
-
C.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
D.
featuresCharacterRescue
Indicates that a work includes a scene or storyline in which one character rescues or saves another.
-
E.
hasCharacterAbility
Indicates that a character possesses or can perform a specific ability.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: April 27, 2026, 6:11 p.m.