Triple

T18014545
Position Surface form Disambiguated ID Type / Status
Subject Star Wars: Hidden Empire E430966 entity
Predicate storyArcPosition P37669 FINISHED
Object third part of the Qi'ra trilogy 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: third part of the Qi'ra trilogy | Statement: [Star Wars: Hidden Empire, storyArcPosition, third part of the Qi'ra trilogy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: storyArcPosition
Context triple: [Star Wars: Hidden Empire, storyArcPosition, third part of the Qi'ra trilogy]
  • A. positionInStory chosen
    Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
  • B. storyArcLength
    Indicates the duration or extent of a narrative arc within a story, such as how long a particular plotline continues.
  • C. stageReached
    Indicates that a process, task, or entity has arrived at or completed a specific stage or phase within a defined progression.
  • D. storyNumber
    Indicates the numerical identifier assigned to a specific story within a collection, sequence, or dataset.
  • E. stakesInStory
    Indicates that one entity has a personal investment, risk, or potential gain/loss tied to the outcome of another entity’s story or narrative.
  • 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_69d8b904530081908bf341d842464856 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4b522e84c8190a03f6445df9f5ac8 completed April 19, 2026, 10:57 a.m.
PD Predicate disambiguation batch_69e3f90039e4819080527f860dca042e completed April 18, 2026, 9:34 p.m.
Created at: April 10, 2026, 10:24 a.m.