Triple
T25440008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petrapole |
E637476
|
entity |
| Predicate | oppositeBorderPost |
P78863
|
FINISHED |
| Object | Benapole land port |
—
|
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: Benapole land port | Statement: [Petrapole, oppositeBorderPost, Benapole land port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppositeBorderPost Context triple: [Petrapole, oppositeBorderPost, Benapole land port]
-
A.
oppositeTownAcrossBorder
chosen
Indicates that one town is located directly across a border from another town, positioned as its opposite counterpart.
-
B.
borderingCountryOnOtherSide
Indicates that one country lies on the opposite side of a shared border relative to another country.
-
C.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
-
D.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
E.
hasBorderPostWith
Indicates that two regions or territories share a border where an official border post or checkpoint is located between them.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 21, 2026, 2 p.m.