Triple
T35309580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prosna |
E1019729
|
entity |
| Predicate | isBorderFor |
P71578
|
FINISHED |
| Object | sections of Greater Poland Voivodeship boundary |
—
|
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: sections of Greater Poland Voivodeship boundary | Statement: [Prosna, isBorderFor, sections of Greater Poland Voivodeship boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBorderFor Context triple: [Prosna, isBorderFor, sections of Greater Poland Voivodeship boundary]
-
A.
isBoundaryFor
chosen
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
B.
hasBorderThrough
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
C.
borderIsAffectedBy
Indicates that a border’s state, condition, or characteristics are influenced or changed by another factor or event.
-
D.
hasBorderRelation
Indicates that one entity shares a boundary or border with another entity.
-
E.
hasBordersBy
Indicates that one entity shares a boundary or border with another entity.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7905415488190bb8114e5373b862f |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.