Triple
T27641967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superman: Red Son |
E696610
|
entity |
| Predicate | hasAlternativeVersionOf |
P5887
|
FINISHED |
| Object | Batman |
—
|
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: Batman | Statement: [Superman: Red Son, hasAlternativeVersionOf, Batman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeVersionOf Context triple: [Superman: Red Son, hasAlternativeVersionOf, Batman]
-
A.
hasAlternativeRadioVersionWith
Indicates that one audio track has a corresponding alternative version specifically edited or mixed for radio play.
-
B.
isAlternativeTo
chosen
Indicates that one entity can serve as a substitute or different option in place of another.
-
C.
hasAlternativeProfile
Indicates that an entity is associated with another profile that serves as an alternative or secondary representation of it.
-
D.
hasAlternativeArrangement
Indicates that one entity can be organized, configured, or structured in a different valid way as an alternative to its current or primary arrangement.
-
E.
hasAlternativeMedium
Indicates that an entity is available, expressed, or presented in another medium or format as an alternative to its primary one.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 2:27 p.m.