Triple
T31509010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danu Self-Administered Zone |
E803892
|
entity |
| Predicate | borderingStateOrRegion |
P88549
|
FINISHED |
| Object | Mandalay Region |
—
|
NE NERFINISHED |
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: Mandalay Region | Statement: [Danu Self-Administered Zone, borderingStateOrRegion, Mandalay Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingStateOrRegion Context triple: [Danu Self-Administered Zone, borderingStateOrRegion, Mandalay Region]
-
A.
borderingStateOrProvince
chosen
Indicates that one state or province shares a common boundary with another state or province.
-
B.
borderingStateOrTerritory
Indicates that one state or territory shares a common boundary with another state or territory.
-
C.
borderStateOf
Indicates that one state shares a common boundary or border with another state.
-
D.
stateBorderContext
Indicates that one state shares a border with another state within a specified geographic or political context.
-
E.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: April 30, 2026, 9:49 p.m.