Triple
T27851952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turbulence |
E703976
|
entity |
| Predicate | hasSuperpoweredCharacters |
P142175
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Turbulence, hasSuperpoweredCharacters, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuperpoweredCharacters Context triple: [Turbulence, hasSuperpoweredCharacters, yes]
-
A.
hasSuperpower
Indicates that one entity possesses a special or extraordinary power or ability beyond normal human capabilities.
-
B.
featuresCharacterWithSuperpowers
chosen
Indicates that the subject includes or portrays a character who possesses superhuman abilities or powers.
-
C.
hasSuperpowersTheme
Indicates that the subject involves, features, or centers around the theme of characters possessing superhuman abilities or powers.
-
D.
superheroStatus
Indicates that an entity possesses the qualities, role, or designation of being a superhero, such as having heroic abilities, identity, or status.
-
E.
hasSuperheroMantle
Indicates that one entity holds or has assumed the superhero identity, title, or role associated with 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 27, 2026, 6:11 p.m.