Triple
T13274002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X: The Man with the X-Ray Eyes |
E316138
|
entity |
| Predicate | featuresSpecialAbility |
P109271
|
FINISHED |
| Object | x-ray vision |
—
|
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: x-ray vision | Statement: [X: The Man with the X-Ray Eyes, featuresSpecialAbility, x-ray vision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSpecialAbility Context triple: [X: The Man with the X-Ray Eyes, featuresSpecialAbility, x-ray vision]
-
A.
featuresPowerUp
Indicates that one entity includes, provides, or incorporates a power-up as part of its content or functionality.
-
B.
featuresStarPower
Indicates that something prominently includes or showcases a highly famous or celebrated person or talent.
-
C.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
D.
speciesAbility
Indicates that a particular species possesses a specific ability or characteristic capacity.
-
E.
notableTraitInMarvel
Indicates that a particular trait or characteristic is especially prominent or noteworthy within the Marvel universe.
- F. None of above. chosen
Provenance (4 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:26 p.m.