Triple
T6189931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jor-El |
E138158
|
entity |
| Predicate | alias |
P39
|
FINISHED |
| Object | Jor El |
E138158
|
NE 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: Jor El | Statement: [Jor-El, alias, Jor El]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jor El Context triple: [Jor-El, alias, Jor El]
-
A.
Darkseid
Darkseid is a powerful cosmic supervillain and ruler of the planet Apokolips in DC Comics, known as one of Superman’s most formidable enemies and a central antagonist in the DC Universe.
-
B.
Metatron
Metatron is a powerful angelic being often depicted in Jewish and Christian mysticism as a celestial scribe or the voice of God.
-
C.
Saoshyant
Saoshyant is the prophesied savior in Zoroastrianism who will lead the final renovation of the world, defeat evil, and bring about the resurrection and ultimate triumph of good.
-
D.
Jor-El
chosen
Jor-El is Superman’s Kryptonian father, a brilliant scientist who foresees his planet’s destruction and sends his infant son to Earth.
-
E.
Korvac
Korvac is a powerful cosmic villain in Marvel Comics best known for battling the Avengers and the Guardians of the Galaxy in the classic "Korvac Saga."
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0621abad48190acb9ec019c065ed4 |
completed | March 22, 2026, 9:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c16f0d5a2881908564442aca29b1ec |
completed | March 23, 2026, 4:49 p.m. |
Created at: March 22, 2026, 4:19 p.m.