Triple
T13186821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Province |
E313876
|
entity |
| Predicate | borderTypeWithNationalCapitalDistrict |
P10768
|
FINISHED |
| Object | land border |
—
|
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: land border | Statement: [Central Province, borderTypeWithNationalCapitalDistrict, land border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTypeWithNationalCapitalDistrict Context triple: [Central Province, borderTypeWithNationalCapitalDistrict, land border]
-
A.
bordersPrefecture
Indicates that one prefecture shares a common boundary with another prefecture.
-
B.
countryBorderType
Indicates the type or nature of the border relationship that exists between two countries.
-
C.
hasBorderCity
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
D.
bordersInternalDivision
Indicates that one administrative or internal division shares a common boundary with another internal division within the same larger entity.
-
E.
borderRegionOf
chosen
Indicates that one region lies along, touches, or forms part of the boundary of another region.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:15 p.m.