Triple
T30736069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civil War: The Initiative |
E782555
|
entity |
| Predicate | setsUpSeries |
P140701
|
FINISHED |
| Object | Mighty Avengers |
—
|
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: Mighty Avengers | Statement: [Civil War: The Initiative, setsUpSeries, Mighty Avengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsUpSeries Context triple: [Civil War: The Initiative, setsUpSeries, Mighty Avengers]
-
A.
testSeriesOf
Indicates that one entity is a test or evaluation designed to be applied sequentially or collectively to a series of related entities.
-
B.
launchesSeries
chosen
Indicates that one entity initiates or starts a sequence or series of related events, actions, or items involving another entity.
-
C.
seriesRun
Indicates that one entity is a specific run, edition, or installment within an ongoing series associated with another entity.
-
D.
seriesWith
Indicates that one entity is part of, or grouped together in, the same series or sequence as another entity.
-
E.
basedInSeriesSetting
Indicates that something (such as a work, event, or element) is situated within or occurs in the primary setting established by a particular 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68ee76a3c819096e4d548a9ca22da |
completed | May 2, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:37 p.m.