Triple
T13966752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poros |
E335942
|
entity |
| Predicate | hasHarborFront |
P44134
|
FINISHED |
| Object | lined with neoclassical buildings |
—
|
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: lined with neoclassical buildings | Statement: [Poros, hasHarborFront, lined with neoclassical buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHarborFront Context triple: [Poros, hasHarborFront, lined with neoclassical buildings]
-
A.
hasHarbor
Indicates that a place possesses or contains a harbor for docking or sheltering vessels.
-
B.
hasHarborCity
Indicates that one entity possesses or is associated with a city that functions as its harbor or port.
-
C.
hasHarborFeature
chosen
Indicates that something possesses or includes a specific harbor-related characteristic, structure, or facility.
-
D.
hasHarbourEntrance
Indicates that an entity serves as the entrance or access point to a harbour for another entity.
-
E.
hasPrivateHarbour
Indicates that an entity possesses or is associated with its own exclusive harbour not shared with the general public.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e8c9e988190a84c9ca8a78b515f |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.