Triple
T38071628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avengers Assemble |
E950599
|
entity |
| Predicate | season4Subtitle |
P188895
|
FINISHED |
| Object | Secret Wars |
—
|
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: Secret Wars | Statement: [Avengers Assemble, season4Subtitle, Secret Wars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: season4Subtitle Context triple: [Avengers Assemble, season4Subtitle, Secret Wars]
-
A.
season4RequiredTitles
Indicates that certain titles or items are required specifically for participation in or access to season 4 of a series, event, or system.
-
B.
season1Subtitle
Indicates that one entity is the subtitle or subheading associated specifically with the first season of another entity.
-
C.
season4Subject
Indicates that one entity serves as the subject or main focus of the fourth season of another entity (such as a series or show).
-
D.
season2Subtitle
Indicates that an entity serves as the subtitle (secondary title or tagline) specifically for the second season of another entity (such as a TV series).
-
E.
seasonSubtitle
chosen
Indicates that a particular text string serves as the subtitle or secondary title for a specific season within a series.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 3, 2026, 4:21 p.m.