Triple

T16841581
Position Surface form Disambiguated ID Type / Status
Subject Borchester E409424 entity
Predicate hasFictionalEconomicRole P2223 FINISHED
Object regional commercial centre 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: regional commercial centre | Statement: [Borchester, hasFictionalEconomicRole, regional commercial centre]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFictionalEconomicRole
Context triple: [Borchester, hasFictionalEconomicRole, regional commercial centre]
  • A. hasEconomicRole chosen
    Indicates that an entity participates in or fulfills a specific function, position, or responsibility within an economic system or activity.
  • B. hasFictionalRole
    Indicates that an entity plays or is assigned a specific role within a fictional work or narrative.
  • C. hasFictionalEconomyBasedOn
    Indicates that one fictional economy is modeled after, inspired by, or structurally derived from another specified economy.
  • D. hasFictionalEconomicActivity
    Indicates that an entity is involved in an economic activity that exists only in a fictional or imaginary context.
  • E. hasFictionalLeader
    Indicates that an entity is led or governed by a leader who is a fictional character rather than a real person.
  • 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_69d883952b048190887740a980b712ed completed April 10, 2026, 4:59 a.m.
NER Named-entity recognition batch_69e3b35167a48190b45a459023e3ab1b completed April 18, 2026, 4:37 p.m.
PD Predicate disambiguation batch_69e32b87b4248190aaddb05e88452356 completed April 18, 2026, 6:58 a.m.
Created at: April 10, 2026, 5:24 a.m.