Triple
T34818661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | เขตดอนเมือง |
E1003705
|
entity |
| Predicate | administrativeOrganization |
P57410
|
FINISHED |
| Object | สำนักงานเขตดอนเมือง |
—
|
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: สำนักงานเขตดอนเมือง | Statement: [เขตดอนเมือง, administrativeOrganization, สำนักงานเขตดอนเมือง]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeOrganization Context triple: [เขตดอนเมือง, administrativeOrganization, สำนักงานเขตดอนเมือง]
-
A.
administrativeAffiliation
chosen
Indicates that one entity is formally connected to, governed by, or overseen by another entity within an administrative or organizational structure.
-
B.
allyOrganization
Indicates that one organization has a cooperative or supportive alliance relationship with another organization.
-
C.
organizationName
Indicates that an entity has a specific official name as an organization.
-
D.
representativeOrganization
Indicates that one organization acts on behalf of, or serves as the official representative of, another entity in some capacity.
-
E.
representedOrganization
Indicates that one entity acts on behalf of, or serves as the official representative of, another organization.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: May 3, 2026, 4 p.m.