Triple
T20408851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radio K.A.O.S. |
E500536
|
entity |
| Predicate | featuresCharacterWithAbility |
P93957
|
FINISHED |
| Object | hears radio waves |
—
|
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: hears radio waves | Statement: [Radio K.A.O.S., featuresCharacterWithAbility, hears radio waves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCharacterWithAbility Context triple: [Radio K.A.O.S., featuresCharacterWithAbility, hears radio waves]
-
A.
featuresSpecialAbility
Indicates that an entity possesses or is characterized by a particular special ability.
-
B.
featuresCharacterWith
chosen
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
C.
hasProtagonistAbility
Indicates that a protagonist possesses a specific ability, power, or special skill.
-
D.
hasSupportingCharacterTrait
Indicates that a supporting character possesses a particular trait, quality, or characteristic.
-
E.
notableTraitInMarvel
Indicates that a particular trait or characteristic is especially prominent or noteworthy within the Marvel universe.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a3d03ac81908f37b907ccbb5088 |
completed | April 20, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:29 a.m.