Triple
T26718606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thailand administrative divisions |
E673634
|
entity |
| Predicate | isFurtherDividedInto |
P45773
|
FINISHED |
| Object | districts |
—
|
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: districts | Statement: [Thailand administrative divisions, isFurtherDividedInto, districts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFurtherDividedInto Context triple: [Thailand administrative divisions, isFurtherDividedInto, districts]
-
A.
dividedIn
Indicates that one entity is partitioned or separated into multiple distinct parts, sections, or groups represented by another entity.
-
B.
sometimesDividedInto
Indicates that an entity is on some occasions partitioned or separated into distinct parts, sections, or groups, but not always.
-
C.
isDividedFrom
Indicates that one entity is separated or partitioned from another, typically by a boundary, barrier, or dividing line.
-
D.
subdividedBy
chosen
Indicates that something is divided into smaller parts or sections by another entity or criterion.
-
E.
divisionAlsoKnownAs
Indicates that one division is alternatively referred to by another name or alias.
- 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_69f617ff3a808190bb5cba40ba93830e |
completed | May 2, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:39 a.m.