Triple
T33344505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic of Zubrowka |
E853758
|
entity |
| Predicate | hasFictionalBorder |
P199023
|
FINISHED |
| Object | neighboring authoritarian states (unnamed) |
—
|
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: neighboring authoritarian states (unnamed) | Statement: [Republic of Zubrowka, hasFictionalBorder, neighboring authoritarian states (unnamed)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalBorder Context triple: [Republic of Zubrowka, hasFictionalBorder, neighboring authoritarian states (unnamed)]
-
A.
hasCountryBorderWith
Indicates that two countries share a common land or maritime boundary.
-
B.
hasBorderWithinCountry
Indicates that one region or area shares an internal boundary with another region or area within the same country.
-
C.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
hasBorderWithNonSovereignEntity
Indicates that one entity shares a land or maritime border with a political or territorial unit that is not fully sovereign.
-
E.
hasBorderCity
Indicates that one location is a city situated on or very near the border of another geographic or political region.
- F. None of above. chosen
Provenance (4 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69ff1ba7494481908678a7a0f93dbd03 |
completed | May 9, 2026, 11:33 a.m. |
Created at: May 1, 2026, 1:34 a.m.