Triple
T18892324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pedagogical College in Gdańsk |
E462119
|
entity |
| Predicate | locatedInCityWithStatus |
P118024
|
FINISHED |
| Object | port city |
—
|
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: port city | Statement: [Pedagogical College in Gdańsk, locatedInCityWithStatus, port city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCityWithStatus Context triple: [Pedagogical College in Gdańsk, locatedInCityWithStatus, port city]
-
A.
basedInCity
Indicates that an entity has its primary location, headquarters, or main operations situated in a specified city.
-
B.
impliesStatusOfCity
chosen
Indicates that one entity suggests, infers, or entails a particular status or condition of a city.
-
C.
hasCityStatusFor
Indicates that an entity holds official city status within the jurisdiction or context of another entity.
-
D.
isCityOf
Indicates that one entity is a city that belongs to, is located within, or is administratively part of another entity (such as a country, state, or region).
-
E.
locatedInPlannedCity
Indicates that something is situated within the boundaries of a city that was deliberately designed and planned rather than having developed organically.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c47bbf908190b141e98e3468e908 |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.