Triple
T32146167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arcane |
E821028
|
entity |
| Predicate | announcedSeason |
P174136
|
FINISHED |
| Object | Arcane Season 2 |
—
|
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: Arcane Season 2 | Statement: [Arcane, announcedSeason, Arcane Season 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedSeason Context triple: [Arcane, announcedSeason, Arcane Season 2]
-
A.
announcedInSeason
Indicates that something (such as a product, feature, or event) was officially announced during a particular season.
-
B.
broadcastSeason
Indicates the time period or season during which something, typically a media work, is broadcast or aired.
-
C.
wonSeasonOf
Indicates that one entity emerged as the overall winner of a particular season of a competition, show, or series involving the other entity.
-
D.
plannedKickoffSeason
Indicates the season during which an event, project, or activity is scheduled to begin or kick off.
-
E.
formedSeason
Indicates that an entity came into existence, was created, or was established during a specific season.
- F. None of above. chosen
Provenance (4 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:31 a.m.