Triple
T38620275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Fantasy XIV: Shadowbringers |
E936846
|
entity |
| Predicate | expandsContent |
P14356
|
FINISHED |
| Object | main scenario quests |
—
|
LITERAL FINISHED |
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: main scenario quests | Statement: [Final Fantasy XIV: Shadowbringers, expandsContent, main scenario quests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandsContent Context triple: [Final Fantasy XIV: Shadowbringers, expandsContent, main scenario quests]
-
A.
expandsContentFor
Indicates that one entity reveals or displays additional content on behalf of or in relation to another entity.
-
B.
editorExpandedContent
Indicates that an editor interface or component is in an expanded (as opposed to collapsed) state, showing additional content or options.
-
C.
expansionContentType
Indicates the type or category of content that is revealed or added when something is expanded.
-
D.
expands
chosen
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
-
E.
expandsIn
Indicates that one entity grows, spreads, or extends its presence or influence within the space, scope, or context defined by another entity.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: May 3, 2026, 4:32 p.m.