Triple
T20571431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 188 |
E505105
|
entity |
| Predicate | borderTypeAtTerminus |
P38214
|
FINISHED |
| Object | international 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: international border | Statement: [SR 188, borderTypeAtTerminus, international border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTypeAtTerminus Context triple: [SR 188, borderTypeAtTerminus, international border]
-
A.
borderTerminus
Indicates the endpoint location where a border between two areas or entities begins or ends.
-
B.
hasBorderTerminus
Indicates that one entity serves as the endpoint or terminal location of another entity’s border or boundary.
-
C.
boundaryTypeEast
Indicates the type or nature of the boundary that lies to the east of a given entity.
-
D.
borderCharacteristic
chosen
Indicates that one entity specifies a property, feature, or quality of the border or boundary of another entity.
-
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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a905b1288190bbad9aa14362bb97 |
completed | April 20, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.