Triple
T31096612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pruszcz Gdański |
E792546
|
entity |
| Predicate | hasNearbyExpressway |
P7229
|
FINISHED |
| Object | S6 expressway |
—
|
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: S6 expressway | Statement: [Pruszcz Gdański, hasNearbyExpressway, S6 expressway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyExpressway Context triple: [Pruszcz Gdański, hasNearbyExpressway, S6 expressway]
-
A.
hasNearbyInternationalRoad
Indicates that an entity is located close to an international road or highway that crosses national borders.
-
B.
hasExpresswaySection
chosen
Indicates that an entity includes, contains, or is associated with a specific section or segment of an expressway.
-
C.
motorwayJunctionNearby
Indicates that a motorway junction is located close to the referenced entity.
-
D.
nearestMotorway
Indicates that one entity is the motorway that is geographically closest to the other entity.
-
E.
hasNearbyTransportationCorridor
Indicates that an entity is located close to a significant transportation route or corridor, such as a road, railway, or transit line.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: April 29, 2026, 9:03 p.m.