Triple

T4378881
Position Surface form Disambiguated ID Type / Status
Subject Dubai Derby E99077 entity
Predicate localSignificance P12510 FINISHED
Object fiercely contested 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: fiercely contested | Statement: [Dubai Derby, localSignificance, fiercely contested]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: localSignificance
Context triple: [Dubai Derby, localSignificance, fiercely contested]
  • A. hasRegionalSignificance chosen
    Indicates that something holds particular importance, influence, or relevance within a specific geographic region.
  • B. hasParticularSignificanceFor
    Indicates that something holds a special, notable, or contextually important relevance or impact for a particular entity or situation.
  • C. significance
    Indicates that one entity holds particular importance, influence, or meaningful impact in relation to another entity or context.
  • D. typeOfSignificance
    Indicates that one entity specifies the nature or category of importance, relevance, or significance that another entity possesses.
  • E. navigationSignificance
    Indicates the degree to which something serves as a meaningful aid or reference point for determining or following a route or direction.
  • 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_69b3454ea8f48190a49c2436624d6ef6 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35240092c81908e26ff607d665e7a completed March 12, 2026, 11:54 p.m.
PD Predicate disambiguation batch_69b34f557fe8819085032bf7f0cea5dc completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:18 p.m.