Triple
T35280020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tales to Astonish #49 |
E1018908
|
entity |
| Predicate | introducesIdentity |
P111286
|
FINISHED |
| Object | Giant-Man |
—
|
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: Giant-Man | Statement: [Tales to Astonish #49, introducesIdentity, Giant-Man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesIdentity Context triple: [Tales to Astonish #49, introducesIdentity, Giant-Man]
-
A.
introducesName
Indicates that one entity presents or gives a name or designation to another entity.
-
B.
introducesSuperheroIdentity
chosen
Indicates that one entity reveals or presents the superhero persona or codename of another entity (or themselves) to an audience or context.
-
C.
publicIdentity
Indicates that an entity’s outward-facing identity or persona is known, presented, or recognized in a public context.
-
D.
identityRevealedIn
Indicates that an entity’s true identity becomes known or disclosed within a specified context, source, or situation.
-
E.
subjectIdentity
Indicates that two or more references correspond to the same underlying entity or individual identity.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:03 p.m.