Triple
T30344234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spy x Family Code: White |
E771830
|
entity |
| Predicate | featuresCharacterAbility |
P181134
|
FINISHED |
| Object | telepathy |
—
|
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: telepathy | Statement: [Spy x Family Code: White, featuresCharacterAbility, telepathy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCharacterAbility Context triple: [Spy x Family Code: White, featuresCharacterAbility, telepathy]
-
A.
featuresSpecialAbility
Indicates that an entity possesses or is characterized by a particular special ability.
-
B.
hasCharacterAbility
chosen
Indicates that a character possesses or can perform a specific 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.
hasCharacterAbilityType
Indicates that an entity possesses a specific type or category of character 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ffebbd9bac8190b3dca4b7252a2278 |
completed | May 10, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69ffe93120a08190a44bb64d052eda78 |
completed | May 10, 2026, 2:10 a.m. |
Created at: April 29, 2026, 7:55 p.m.