Triple
T23891295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frankobrod nad Wódroju |
E600775
|
entity |
| Predicate | sharesBorderAcrossRiverWith |
P143613
|
FINISHED |
| Object | Słubice |
—
|
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: Słubice | Statement: [Frankobrod nad Wódroju, sharesBorderAcrossRiverWith, Słubice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesBorderAcrossRiverWith Context triple: [Frankobrod nad Wódroju, sharesBorderAcrossRiverWith, Słubice]
-
A.
bordersAcrossRiver
chosen
Indicates that two regions or entities share a boundary with each other that is separated or defined by a river.
-
B.
borderedByCountryAcrossRiver
Indicates that one country shares a border with another country, with the boundary specifically formed or separated by a river.
-
C.
riverCrossingConnection
Indicates a connection between two locations that are linked by a route or structure specifically used to cross a river.
-
D.
hasRiverCrossingType
Indicates the type or nature of a river crossing associated with an entity (e.g., bridge, ford, ferry).
-
E.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
- 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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cd036dd48190be508063b18762a4 |
completed | April 29, 2026, 9:18 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:25 p.m.