Triple
T38655375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Fantasy XIV: Endwalker |
E939876
|
entity |
| Predicate | addsRaidSeries |
P183436
|
FINISHED |
| Object | Pandaemonium |
—
|
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: Pandaemonium | Statement: [Final Fantasy XIV: Endwalker, addsRaidSeries, Pandaemonium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsRaidSeries Context triple: [Final Fantasy XIV: Endwalker, addsRaidSeries, Pandaemonium]
-
A.
addsRaid
chosen
Indicates that an entity initiates or includes a raid event or operation involving another entity.
-
B.
addsTrialSeries
Indicates that an entity initiates or appends a trial series to an existing collection, schedule, or experimental setup.
-
C.
associatedRaid
Indicates a relationship where one entity is linked to or involved with a particular raid event or operation.
-
D.
releaseSeries
Indicates that one entity publishes or makes available a sequence of related releases (such as episodes, issues, or installments) as part of an ongoing series.
-
E.
supportSeriesOf
Indicates a relationship where one entity provides ongoing backing or assistance to a sequence or set of related actions, events, or items.
- 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.