Triple
T38262344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gdynia–Kościerzyna railway line |
E1017959
|
entity |
| Predicate | terminusCityIsPort |
P191746
|
FINISHED |
| Object | Gdynia |
—
|
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: Gdynia | Statement: [Gdynia–Kościerzyna railway line, terminusCityIsPort, Gdynia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusCityIsPort Context triple: [Gdynia–Kościerzyna railway line, terminusCityIsPort, Gdynia]
-
A.
terminusCity
Indicates that a transportation route or service ends or has its final stop in a particular city.
-
B.
terminusLocatedOn
Indicates that the endpoint or final stop of one entity (such as a route or line) is situated on or at another entity (such as a street, line, or location).
-
C.
terminusCitySouth
Indicates that something serves as the southern terminus or endpoint located in a particular city.
-
D.
terminusCityArea
Indicates that a city area serves as the terminal or end-point location for a route, line, or journey.
-
E.
terminusCitySouthwest
Indicates that the terminus (end point) of something is located to the southwest of a specified city.
- 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:30 p.m.