Triple
T37591737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Fantasy XIV: Stormblood |
E935275
|
entity |
| Predicate | addsTrialSeries |
P188744
|
FINISHED |
| Object | The Four Lords |
—
|
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 Four Lords | Statement: [Final Fantasy XIV: Stormblood, addsTrialSeries, The Four Lords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsTrialSeries Context triple: [Final Fantasy XIV: Stormblood, addsTrialSeries, The Four Lords]
-
A.
placeInSeries
Indicates the position or order that something occupies within a sequence or series.
-
B.
seriesWith
Indicates that one entity is part of, or grouped together in, the same series or sequence as another entity.
-
C.
seriesRun
Indicates that one entity is a specific run, edition, or installment within an ongoing series associated with another entity.
-
D.
seriesOf
Indicates that one entity is a sequence or ordered set of related items, events, or parts that collectively form or belong to another entity.
-
E.
launchesSeries
Indicates that one entity initiates or starts a sequence or series of related events, actions, or items involving another entity.
- 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_69f76ecf39c081909baffe597bb55273 |
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. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:18 p.m.