Triple
T29525318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volos municipality |
E749050
|
entity |
| Predicate | isPortCityMunicipality |
P163356
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Volos municipality, isPortCityMunicipality, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPortCityMunicipality Context triple: [Volos municipality, isPortCityMunicipality, true]
-
A.
isPortMunicipality
chosen
Indicates that a municipality functions as a port, having facilities for maritime transport and related activities.
-
B.
isPortCityOn
Indicates that a city functions as a port located on the specified body of water.
-
C.
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.
-
D.
hasPortCity
Indicates that a place or region possesses or is associated with a city that functions as its port.
-
E.
hasPortCityCharacteristicsOf
Indicates that one entity possesses or exhibits the defining features, functions, or qualities typically associated with a port city of another entity.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c9c43c081908f30ae295f032c95 |
completed | May 2, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:45 p.m.