Triple

T26718584
Position Surface form Disambiguated ID Type / Status
Subject Thailand administrative divisions E673634 entity
Predicate hasSecondLevelUnit P53398 FINISHED
Object district 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: district | Statement: [Thailand administrative divisions, hasSecondLevelUnit, district]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSecondLevelUnit
Context triple: [Thailand administrative divisions, hasSecondLevelUnit, district]
  • A. hasSecondLevel
    Indicates that an entity possesses or is associated with a second hierarchical level within a structured system or classification.
  • B. hasSecondLevelAdministrativeTerritory chosen
    Indicates that an entity possesses or includes a second-level administrative division within its territorial or organizational hierarchy.
  • C. hasSecondLineUpperLevel
    Indicates that an entity possesses a second line located on an upper level or tier relative to a primary or lower line.
  • D. hasSecondary
    Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
  • E. hasUnitLevel
    Indicates that something is associated with, measured at, or applicable to a specific unit level within a larger hierarchy or scale.
  • 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_69eecda481d08190aea69f2f7c745f56 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69f7bbf906d8819099020e548dd56bc9 completed May 3, 2026, 9:19 p.m.
PD Predicate disambiguation batch_69f7b9a2dcf88190a7c9e109e41267be completed May 3, 2026, 9:09 p.m.
Created at: April 27, 2026, 3:39 a.m.