Triple
T24376217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeppes Reef border post |
E614480
|
entity |
| Predicate | neighbouringCountryCodeSide |
P121780
|
FINISHED |
| Object | SZ |
—
|
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: SZ | Statement: [Jeppes Reef border post, neighbouringCountryCodeSide, SZ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighbouringCountryCodeSide Context triple: [Jeppes Reef border post, neighbouringCountryCodeSide, SZ]
-
A.
neighboringCountryPresence
Indicates that one country has a geographic presence (such as territory, bases, or influence) in or immediately adjacent to a neighboring country.
-
B.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
-
C.
countryCodeNorthSide
chosen
Indicates that an entity is located on or associated with the northern side of a country identified by a specific country code.
-
D.
hasNeighboringCountryToNorth
Indicates that one country is directly adjacent to and located south of another country, which lies to its north.
-
E.
borderingCountryNearby
Indicates that one country is geographically close to, but does not necessarily share a direct land border with, another country.
- 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_69e2d7e1e010819098b95eb3f905943d |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293d73c0c8190b80e257845a04c57 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:02 a.m.