Triple

T33285173
Position Surface form Disambiguated ID Type / Status
Subject Corleone crime family E852162 entity
Predicate hasFictionalOriginPlace P49286 FINISHED
Object Corleone, Sicily 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: Corleone, Sicily | Statement: [Corleone crime family, hasFictionalOriginPlace, Corleone, Sicily]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFictionalOriginPlace
Context triple: [Corleone crime family, hasFictionalOriginPlace, Corleone, Sicily]
  • A. 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.
  • B. basedInFictionalLocation chosen
    Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
  • C. hasFictionalLandmark
    Indicates that one entity includes, features, or is associated with a landmark that is fictional rather than real.
  • D. hasFictionalTownBasedOn
    Indicates that a fictional town is modeled on, inspired by, or derived from a specific real-world town or location.
  • E. hasBranchInFictionalLocation
    Indicates that an organization maintains a branch, office, or presence within a fictional or imaginary location.
  • 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_69f349660ff48190a4568803d0b89941 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69ff136ed2a881908f713401083970d1 completed May 9, 2026, 10:58 a.m.
PD Predicate disambiguation batch_69ff10f9e3448190b6cb6ea5a67713c1 completed May 9, 2026, 10:48 a.m.
Created at: May 1, 2026, 1:32 a.m.