Triple

T15066010
Position Surface form Disambiguated ID Type / Status
Subject Bad Wolf Bay E379756 entity
Predicate inUniverseFeature P117183 FINISHED
Object remote beach 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: remote beach | Statement: [Bad Wolf Bay, inUniverseFeature, remote beach]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inUniverseFeature
Context triple: [Bad Wolf Bay, inUniverseFeature, remote beach]
  • A. inUniverseFunction
    Indicates that one entity serves a specific role, purpose, or function within the context or rules of a particular fictional or defined universe.
  • B. inUniverseType
    Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
  • C. inUniverse
    Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
  • D. 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).
  • E. inUniverseOrigin
    Indicates that one entity originates from, or has its source within, the fictional universe or setting defined by another 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_69d85cd7683881908d405c1b5d7b4f7f completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69dedeea750c819082d8823c9ab6c5a2 completed April 15, 2026, 12:42 a.m.
PD Predicate disambiguation batch_69deb95a182081908fffc4402b02a394 completed April 14, 2026, 10:02 p.m.
PDg Predicate description generation batch_69dec71e8dcc81908badc834b6ccf273 completed April 14, 2026, 11 p.m.
Created at: April 10, 2026, 3:02 a.m.