Triple
T24146873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Braniewo County |
E598409
|
entity |
| Predicate | containsPortTown |
P2745
|
FINISHED |
| Object | Frombork |
E132155
|
NE 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: Frombork | Statement: [Braniewo County, containsPortTown, Frombork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPortTown Context triple: [Braniewo County, containsPortTown, Frombork]
-
A.
isPortTown
Indicates that a town is located on or near a navigable body of water and functions as a port for maritime or river transport and trade.
-
B.
hasPortTownService
Indicates that a service or connection is available between a port and a town.
-
C.
hasPortCity
chosen
Indicates that a place or region possesses or is associated with a city that functions as its port.
-
D.
isHomePortOf
Indicates that a particular location serves as the primary base or port where a vessel or fleet is officially registered, stationed, or regularly returns.
-
E.
isPortOfCallFor
Indicates that a location serves as a scheduled stop or destination for a ship, vehicle, or journey.
- F. None of above.
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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e00b00708190bcd1d0b855230378 |
completed | April 29, 2026, 10:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0fc9a489e8819088579c8423725b8e |
completed | May 22, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:29 p.m.