Triple

T33739321
Position Surface form Disambiguated ID Type / Status
Subject The Scousers E864515 entity
Predicate fictionalEthnicOrRegionalIdentity P59975 FINISHED
Object Scouse 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: Scouse | Statement: [The Scousers, fictionalEthnicOrRegionalIdentity, Scouse]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fictionalEthnicOrRegionalIdentity
Context triple: [The Scousers, fictionalEthnicOrRegionalIdentity, Scouse]
  • A. fictionalEthnoCulturalIdentity chosen
    Indicates that an entity is associated with an invented or imaginary ethnic or cultural identity, rather than a real-world one.
  • B. fictionalRegionalIdentity
    Indicates that an entity is associated with, or characterized by, an invented or imaginary regional or local identity.
  • C. fictionalEthnicFocus
    Indicates that something is primarily concerned with, centered on, or thematically emphasizes a fictional or invented ethnic group.
  • D. hasEthnicityInFiction
    Indicates that a fictional character or entity is portrayed as having a particular ethnicity within a narrative or fictional context.
  • E. fictionalCitizenship
    Indicates that an entity is recognized as a citizen of a fictional or imaginary polity, realm, or jurisdiction.
  • 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_69f3498b24b8819096a65009e521d0e1 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fe8f74748c8190bd14a856c057f9f7 completed May 9, 2026, 1:35 a.m.
PD Predicate disambiguation batch_69fe8e7ed8088190929e0df67aca4de9 completed May 9, 2026, 1:31 a.m.
Created at: May 1, 2026, 1:44 a.m.