Triple
T30345320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALfheim Online |
E771853
|
entity |
| Predicate | successorToInUniverse |
P78292
|
FINISHED |
| Object | Sword Art Online (game) |
—
|
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: Sword Art Online (game) | Statement: [ALfheim Online, successorToInUniverse, Sword Art Online (game)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorToInUniverse Context triple: [ALfheim Online, successorToInUniverse, Sword Art Online (game)]
-
A.
inUniverseSuccessor
chosen
Indicates that one entity is the next or following entity in sequence within a particular fictional or defined universe or continuity.
-
B.
successorInTheory
Indicates that one entity directly follows and replaces another within a specified theoretical framework or system.
-
C.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
D.
successorUsedIn
Indicates that a successor entity is utilized or referenced within the context, operation, or implementation of another entity.
-
E.
successorDeterminedBy
Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: April 29, 2026, 7:55 p.m.