Triple
T38093211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challengers of the Unknown |
E951168
|
entity |
| Predicate | creatorRealNameOfJackKirby |
P119633
|
FINISHED |
| Object | Jacob Kurtzberg |
—
|
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: Jacob Kurtzberg | Statement: [Challengers of the Unknown, creatorRealNameOfJackKirby, Jacob Kurtzberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creatorRealNameOfJackKirby Context triple: [Challengers of the Unknown, creatorRealNameOfJackKirby, Jacob Kurtzberg]
-
A.
authorRealNameOfCreator
chosen
Indicates that a person’s real, legal, or birth name is the true identity behind a creator who may be known by a pseudonym or handle.
-
B.
creatorInComics
Indicates that one entity is the creator (such as writer or artist) responsible for the content or characters appearing in a particular comic work or series.
-
C.
creatorBirthName
Indicates the full birth name originally given to the creator of a work or entity.
-
D.
creatorAlternativeName
Indicates an alternative or variant name used to refer to the creator.
-
E.
metJerrySiegelWhen
Indicates that one entity first encountered or became acquainted with Jerry Siegel at a particular time or event.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00053d8004819097ad9cf6431a20a3 |
completed | May 10, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_6a0004b3a82c81908e2bf9a533a93eb6 |
completed | May 10, 2026, 4:08 a.m. |
Created at: May 3, 2026, 4:21 p.m.