Triple

T28904598
Position Surface form Disambiguated ID Type / Status
Subject government of Oceania E733038 entity
Predicate governsFictionalPlace P163692 FINISHED
Object Oceania 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: Oceania | Statement: [government of Oceania, governsFictionalPlace, Oceania]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governsFictionalPlace
Context triple: [government of Oceania, governsFictionalPlace, Oceania]
  • A. fictionalLocationGoverned chosen
    Indicates that a fictional location is under the authority, control, or administration of a particular governing entity within a narrative or imagined setting.
  • B. stateOfFictionalLocation
    Indicates that a fictional location is situated within or belongs to a particular state or state-like administrative region.
  • C. worksAtFictionalPlace
    Indicates that an entity is employed at or associated with performing work in a fictional or imaginary location.
  • D. basedInFictionalLocation
    Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
  • E. hasFictionalLocation
    Indicates that an entity is associated with, set in, or takes place within a location that exists only in fiction rather than in the real world.
  • 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_69f05b096d208190958a57d2e4b5a93a completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69fec00f27988190955de6b6348a4d97 completed May 9, 2026, 5:03 a.m.
PD Predicate disambiguation batch_69febd52037c8190b475dbd50fdbc13e completed May 9, 2026, 4:51 a.m.
Created at: April 28, 2026, 8:05 a.m.