Triple

T37539645
Position Surface form Disambiguated ID Type / Status
Subject Final Fantasy XIV: Heavensward E933291 entity
Predicate expandsMainScenario P8787 FINISHED
Object post–A Realm Reborn storyline 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: post–A Realm Reborn storyline | Statement: [Final Fantasy XIV: Heavensward, expandsMainScenario, post–A Realm Reborn storyline]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: expandsMainScenario
Context triple: [Final Fantasy XIV: Heavensward, expandsMainScenario, post–A Realm Reborn storyline]
  • A. trajectoryExpansion
    Indicates how the path or course of something spreads, widens, or diversifies over time or space.
  • B. extendedInCase
    Indicates that one entity is lengthened, prolonged, or expanded when a particular condition or case applies.
  • C. expandedAction
    Indicates an action that has been elaborated, detailed, or extended beyond its original or basic form.
  • D. expandsIn chosen
    Indicates that one entity grows, spreads, or extends its presence or influence within the space, scope, or context defined by another entity.
  • E. expansionProject
    Indicates a project whose primary purpose is to enlarge, extend, or increase the capacity, scope, or reach of something.
  • 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_69fd35d108908190b79b1e8e6bbd62aa completed May 8, 2026, 1:01 a.m.
PD Predicate disambiguation batch_69fd34cb46108190b43c3b7f67ec4cd4 completed May 8, 2026, 12:56 a.m.
Created at: May 3, 2026, 4:17 p.m.