Triple
T37539634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Fantasy XIV: Heavensward |
E933291
|
entity |
| Predicate | addsAllianceRaid |
P100069
|
FINISHED |
| Object | The Void Ark |
—
|
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: The Void Ark | Statement: [Final Fantasy XIV: Heavensward, addsAllianceRaid, The Void Ark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsAllianceRaid Context triple: [Final Fantasy XIV: Heavensward, addsAllianceRaid, The Void Ark]
-
A.
addsRaid
Indicates that an entity initiates or includes a raid event or operation involving another entity.
-
B.
associatedRaid
chosen
Indicates a relationship where one entity is linked to or involved with a particular raid event or operation.
-
C.
addsAlliedRace
Indicates establishing or registering an additional race as an ally or allied faction in relation to another entity.
-
D.
allianceFlank
Indicates a cooperative maneuver where allied entities position themselves on the side of a common target or objective to gain a tactical advantage.
-
E.
associatedInvaders
Indicates that certain invaders are linked or connected to a given entity, context, or event in a relevant way.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.