Triple
T14876770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tales of Suspense #39 |
E349886
|
entity |
| Predicate | coverTagline |
P64807
|
FINISHED |
| Object | Who? Or What, Is the New Iron Man of Today? |
—
|
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: Who? Or What, Is the New Iron Man of Today? | Statement: [Tales of Suspense #39, coverTagline, Who? Or What, Is the New Iron Man of Today?]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverTagline Context triple: [Tales of Suspense #39, coverTagline, Who? Or What, Is the New Iron Man of Today?]
-
A.
hasTagline
Indicates that an entity is associated with a specific slogan or tagline that represents or promotes it.
-
B.
taglineForm
Indicates that one entity serves as the tagline or slogan associated with another entity.
-
C.
taglineMatch
Indicates that two entities share the same tagline or that a tagline corresponds to a given entity.
-
D.
coverText
chosen
Indicates that one text serves as the cover or front-facing textual representation for another work or resource.
-
E.
coverSymbol
Indicates that one symbol or notation is used as a cover or representative marker for another entity in a given context.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e4e4448190a8796573bc6d1069 |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:55 a.m.