Triple

T18845864
Position Surface form Disambiguated ID Type / Status
Subject ISO 3166-2:OM E460910 entity
Predicate subdivisionTypeCovered P36805 FINISHED
Object governorates of Oman 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: governorates of Oman | Statement: [ISO 3166-2:OM, subdivisionTypeCovered, governorates of Oman]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: subdivisionTypeCovered
Context triple: [ISO 3166-2:OM, subdivisionTypeCovered, governorates of Oman]
  • A. subdivisionType0
    Indicates that the referenced entity is classified as the primary (level 0) type of administrative or territorial subdivision within a larger jurisdiction.
  • B. hasTypeOfSubdivision chosen
    Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
  • C. subdivisionStatus
    Indicates the current state or phase of a subdivision process or classification for an entity.
  • D. typeOfDiscriminationCovered
    Indicates that a particular kind or category of discriminatory behavior is included within the scope of protections, rules, or analysis.
  • E. typeOfCoverage
    Indicates the specific kind or category of coverage that applies in a given context (such as insurance, service, or protection).
  • 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_69d8dcfa11e4819090ab1ef5bdcd2b2e completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5b8ee96988190bf247b986777945c completed April 20, 2026, 5:26 a.m.
PD Predicate disambiguation batch_69e48d1e7dac81909ea1e758c87773c5 completed April 19, 2026, 8:06 a.m.
Created at: April 10, 2026, 11:56 a.m.