Triple

T4862104
Position Surface form Disambiguated ID Type / Status
Subject Bayou Bucket E108684 entity
Predicate geographicRivalryType P39611 FINISHED
Object intra-city rivalry 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: intra-city rivalry | Statement: [Bayou Bucket, geographicRivalryType, intra-city rivalry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: geographicRivalryType
Context triple: [Bayou Bucket, geographicRivalryType, intra-city rivalry]
  • A. geographicRivalry chosen
    Indicates a competitive or adversarial relationship between entities that arises from their geographic proximity, territorial interests, or spatial influence.
  • B. countryContestedBy
    Indicates that control, ownership, or sovereignty over a country is disputed by multiple parties or entities.
  • C. conflictRegion
    Indicates that the entities are located in or associated with a geographic area characterized by active or recent conflict, tension, or hostilities.
  • D. regionOfConflict
    Indicates that a specified region is the location where a particular conflict or dispute takes place.
  • E. geopoliticalOrigin
    Indicates the geopolitical entity (such as a country, region, or state) from which something or someone originates or is associated.
  • 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_69bd440b965081908b0557721cae6338 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6d5f62b48190b367ed1b850cfbcb completed March 20, 2026, 3:53 p.m.
PD Predicate disambiguation batch_69bd6c27334481909ba8ac80854f7d8e completed March 20, 2026, 3:47 p.m.
Created at: March 20, 2026, 1:26 p.m.