Triple
T27045222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satun |
E684603
|
entity |
| Predicate | hasProvincialGovernmentOffice |
P40692
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Satun, hasProvincialGovernmentOffice, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProvincialGovernmentOffice Context triple: [Satun, hasProvincialGovernmentOffice, true]
-
A.
hasProvinceGovernment
Indicates that a province is administered or governed by a specific provincial government authority.
-
B.
provincialGovernmentAtLocation
chosen
Indicates that a provincial-level government is situated or operates at a specific geographic location.
-
C.
hasLocalGovernmentOffice
Indicates that a local government office is present or established within a specified location or jurisdiction.
-
D.
hasProvincialCouncil
Indicates that an entity possesses or is governed by a provincial-level council as part of its administrative or organizational structure.
-
E.
hasPrefecturalOffice
Indicates that a given location or administrative unit contains or hosts an official prefectural government office.
- 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_69ef148193c48190bb1a0cfae6a407c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: April 27, 2026, 8:09 a.m.