Triple

T24250816
Position Surface form Disambiguated ID Type / Status
Subject Catherine Cleary Wolters E603518 entity
Predicate hasRealityCounterpartInFiction P155333 FINISHED
Object Alex Vause 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: Alex Vause | Statement: [Catherine Cleary Wolters, hasRealityCounterpartInFiction, Alex Vause]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRealityCounterpartInFiction
Context triple: [Catherine Cleary Wolters, hasRealityCounterpartInFiction, Alex Vause]
  • A. isSetInFictionalUniverse
    Indicates that a narrative work takes place within a specific fictional universe or setting.
  • B. livesInFiction
    Indicates that one entity exists or resides within the fictional world or narrative setting created by another entity.
  • C. worksInFictionalContext
    Indicates that an entity performs work or fulfills a role within a fictional or imagined setting rather than in real-world circumstances.
  • D. activeInFictionalUniverse
    Indicates that an entity participates, operates, or has a role within a specified fictional universe or setting.
  • E. hasFictionalUniverseElement
    Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other 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_69e29540da0481909a38bdae315b7a02 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f28b89eb8081909ccf37081add5cee completed April 29, 2026, 10:51 p.m.
PD Predicate disambiguation batch_69f1c450aa508190bc9d372a5f6ee47a completed April 29, 2026, 8:41 a.m.
PDg Predicate description generation batch_69f1c6d4e99081909f61899eccafb73e completed April 29, 2026, 8:52 a.m.
Created at: April 18, 2026, 12:04 a.m.