Triple
T28976061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tales of Suspense |
E734412
|
entity |
| Predicate | captainAmericaFeatureBeganWithIssue |
P78612
|
FINISHED |
| Object | 59 |
—
|
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: 59 | Statement: [Tales of Suspense, captainAmericaFeatureBeganWithIssue, 59]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captainAmericaFeatureBeganWithIssue Context triple: [Tales of Suspense, captainAmericaFeatureBeganWithIssue, 59]
-
A.
captainNorthAmerica
Indicates that one entity serves as the captain or leader of a team, group, or organization associated with North America.
-
B.
firstAppearanceInComicsIssue
chosen
Indicates the specific comic book issue in which an entity (such as a character or item) is depicted for the first time.
-
C.
currentSeriesIssueStart
Indicates that something marks the starting point or first issue of the current series.
-
D.
mainSeriesFirstAppearance
Indicates the work or installment in which an entity first appears within the primary or main series continuity.
-
E.
mainSupermanBatmanTeamUpStartIssue
Indicates the comic issue in which Superman and Batman first officially team up as the primary featured partnership.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65ee10fa4819092019f83769abbd6 |
completed | May 2, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:08 a.m.