Triple

T14227344
Position Surface form Disambiguated ID Type / Status
Subject ZESCO E352655 entity
Predicate hasMonopolyStatus P49261 FINISHED
Object dominant utility in Zambia 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: dominant utility in Zambia | Statement: [ZESCO, hasMonopolyStatus, dominant utility in Zambia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMonopolyStatus
Context triple: [ZESCO, hasMonopolyStatus, dominant utility in Zambia]
  • A. isMonopoly chosen
    Indicates that one entity exclusively controls a market or resource, facing no significant competition.
  • B. monopolyGrantedBy
    Indicates that one party has been given exclusive control or rights over a market, resource, or activity by another authority or entity.
  • C. monopolyConfirmedBy
    Indicates that the existence or status of a monopoly is validated or officially recognized by a specified confirming party or source.
  • D. monopolyOn
    Indicates that one entity has exclusive control or rights over a resource, market, or activity, preventing others from participating on equal terms.
  • E. monopolyPrecededBy
    Indicates that one monopoly situation or period occurred after and was temporally preceded by another specified event, condition, or monopoly.
  • 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_69d8278adc7c8190a9218d69bce3c4e6 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de622a48508190bbfedb762bd1674d completed April 14, 2026, 3:50 p.m.
PD Predicate disambiguation batch_69de05bf069c8190b69f00f00f5eb126 completed April 14, 2026, 9:15 a.m.
Created at: April 10, 2026, 1:07 a.m.