Triple

T35013625
Position Surface form Disambiguated ID Type / Status
Subject Green Pact E1009995 entity
Predicate inUniverseGame P47705 FINISHED
Object The Elder Scrolls Online 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 Elder Scrolls Online | Statement: [Green Pact, inUniverseGame, The Elder Scrolls Online]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inUniverseGame
Context triple: [Green Pact, inUniverseGame, The Elder Scrolls Online]
  • A. inUniverseUse
    Indicates that something is used or occurs within a particular fictional or conceptual universe, as opposed to in the real world or another setting.
  • B. inUniverseActivity
    Indicates that an activity or event occurs within the fictional universe or narrative world of a work, rather than outside it (e.g., in real life or meta-context).
  • C. inUniverseSystem
    Indicates that one entity exists or operates within the scope, rules, or continuity of a particular fictional or conceptual universe or system.
  • D. inUniverse chosen
    Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
  • E. inUniverseRegion
    Indicates that an entity is located within or belongs to a specific universe-defined region or area.
  • 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_69f76dcc3ac8819096a3ed52f5fa2523 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fbc9d1dba881908c399b8e1dc13ce2 completed May 6, 2026, 11:08 p.m.
PD Predicate disambiguation batch_69fbc8ec03ac8190a757563f96fab283 completed May 6, 2026, 11:04 p.m.
Created at: May 3, 2026, 4:01 p.m.