Triple

T175238
Position Surface form Disambiguated ID Type / Status
Subject Persian Gulf E3558 entity
Predicate hasDisputedNaming P3572 FINISHED
Object true 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: true | Statement: [Persian Gulf, hasDisputedNaming, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDisputedNaming
Context triple: [Persian Gulf, hasDisputedNaming, true]
  • A. statusDisputedBy
    Indicates that the validity, accuracy, or recognition of a status is being challenged or contested by a specified party.
  • B. contestedBy
    Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
  • C. usesNamingSystem
    Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
  • D. hasDisputeHistory chosen
    Indicates that there has been at least one prior dispute or conflict involving the related entities.
  • E. endedConflict
    Indicates that a previously ongoing conflict between entities has been brought to an end.
  • 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_69a25374990081909766d30c79a18e0e completed Feb. 28, 2026, 2:31 a.m.
NER Named-entity recognition batch_69a258e32da88190ad9485aecd0bf08f completed Feb. 28, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69a25669d99481908c5e82ba8641205a completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:39 a.m.