Triple
T17911982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superman Family |
E447836
|
entity |
| Predicate | includesNonKryptonianAllies |
P124379
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Superman Family, includesNonKryptonianAllies, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesNonKryptonianAllies Context triple: [Superman Family, includesNonKryptonianAllies, true]
-
A.
associatedCharacters
Indicates that two or more characters are linked or connected through some relationship, involvement, or relevance to each other.
-
B.
alliesInFiction
chosen
Indicates that two or more entities are portrayed as allies or cooperative partners within a fictional context or narrative.
-
C.
roleInLanternEntertainment
Indicates that an entity holds or held a specific role or position within Lantern Entertainment.
-
D.
relationshipToMarvelUniverse
Indicates the nature or type of connection an entity has to the Marvel universe, such as affiliation, role, or relevance within that fictional setting.
-
E.
relationshipWithTitans
Indicates a relationship or association that an entity has with one or more Titans, such as alliances, conflicts, or other significant interactions.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49ea0ea008190b54a999e0704fb67 |
completed | April 19, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.