Triple
T34950590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terespol–Brest |
E1007979
|
entity |
| Predicate | regionPolishSide |
P192043
|
FINISHED |
| Object | Lublin Voivodeship |
—
|
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: Lublin Voivodeship | Statement: [Terespol–Brest, regionPolishSide, Lublin Voivodeship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionPolishSide Context triple: [Terespol–Brest, regionPolishSide, Lublin Voivodeship]
-
A.
sharesBorderWithPolishVoivodeship
chosen
Indicates that one entity has a land or water boundary directly adjoining a Polish voivodeship.
-
B.
hasCityOnPolishSide
Indicates that a given entity has a city located on the Polish side of a border or within Polish territory.
-
C.
objectivePoland
Indicates that something has Poland as its goal, target, or intended destination.
-
D.
isPolish
Indicates that an entity has the property of being Polish, typically in terms of nationality, origin, or cultural affiliation.
-
E.
roleInPoland
Indicates that an entity holds or has held a specific role, position, or function within the context of Poland.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffa15d53208190ab8574d6c7913e18 |
completed | May 9, 2026, 9:04 p.m. |
| PD | Predicate disambiguation | batch_69ff9eee681c81909434e79c627cb528 |
completed | May 9, 2026, 8:54 p.m. |
Created at: May 3, 2026, 4 p.m.