Triple

T6649660
Position Surface form Disambiguated ID Type / Status
Subject Derby della Mole E150787 entity
Predicate localRivalryAspect P18267 FINISHED
Object competition for supremacy in Turin 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: competition for supremacy in Turin | Statement: [Derby della Mole, localRivalryAspect, competition for supremacy in Turin]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: localRivalryAspect
Context triple: [Derby della Mole, localRivalryAspect, competition for supremacy in Turin]
  • A. hasLocalRivalry chosen
    Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
  • B. cityRivalry
    Indicates a competitive or adversarial relationship that exists between two cities, often involving sports, economics, culture, or historical tensions.
  • C. hasRivalryAspect
    Indicates that there exists a competitive or adversarial relationship or dimension between entities.
  • D. conferenceRivalry
    Indicates a competitive or adversarial relationship between entities that belong to the same conference or organized grouping.
  • E. rivalryBasis
    Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
  • 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_69c687f2c9508190a60b9aad31d3f358 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6cc9c6cb0819084fec8e0beb430de completed March 27, 2026, 6:29 p.m.
PD Predicate disambiguation batch_69c6ad04d66c8190926ffcbff372643b completed March 27, 2026, 4:15 p.m.
Created at: March 27, 2026, 2:01 p.m.