Triple
T26718582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thailand administrative divisions |
E673634
|
entity |
| Predicate | hasTopLevelUnit |
P10192
|
FINISHED |
| Object | province |
—
|
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: province | Statement: [Thailand administrative divisions, hasTopLevelUnit, province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTopLevelUnit Context triple: [Thailand administrative divisions, hasTopLevelUnit, province]
-
A.
hasTopLevel
Indicates that one entity is the highest or primary element within a hierarchy or structure relative to another entity.
-
B.
hasUpperLevelFunction
Indicates that one function operates at a higher or more abstract level than another function within a hierarchical relationship.
-
C.
hasTopLevelCategory
Indicates that an entity is assigned to a primary or highest-level category within a classification or taxonomy.
-
D.
topLevelOf
chosen
Indicates that one entity is the highest or most overarching level within the structure or hierarchy of another entity.
-
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_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 3:39 a.m.