Triple

T34735356
Position Surface form Disambiguated ID Type / Status
Subject Mount Qasioun E1001322 entity
Predicate hasToponymInLanguage P24399 FINISHED
Object Arabic 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: Arabic | Statement: [Mount Qasioun, hasToponymInLanguage, Arabic]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasToponymInLanguage
Context triple: [Mount Qasioun, hasToponymInLanguage, Arabic]
  • A. hasLanguageOfToponym chosen
    Indicates that a place name (toponym) is expressed in or associated with a particular language.
  • B. hasOfficialLanguageOfToponym
    Indicates that a toponym is associated with an official language in which that place name is formally recognized or used.
  • C. includesToponym
    Indicates that one entity contains or references a place name (toponym) associated with another entity.
  • D. hasToponymicForm
    Indicates that one entity is a toponymic (place-name-based) form or variant derived from another entity.
  • E. isToponymIn
    Indicates that a place name (toponym) is located within or refers to a specific geographic area or region.
  • 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_69f76daf739881909ed3554f98a2b433 completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69fd2cf39b0c8190811b8a6fa9410560 completed May 8, 2026, 12:23 a.m.
PD Predicate disambiguation batch_69fd2ad8dd988190a9899701ba00d917 completed May 8, 2026, 12:14 a.m.
Created at: May 3, 2026, 3:59 p.m.