Triple
T38572225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Harbour |
E929305
|
entity |
| Predicate | hasDirectionWithinHarbour |
P87968
|
FINISHED |
| Object | eastern section of Granton Harbour |
—
|
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: eastern section of Granton Harbour | Statement: [Eastern Harbour, hasDirectionWithinHarbour, eastern section of Granton Harbour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionWithinHarbour Context triple: [Eastern Harbour, hasDirectionWithinHarbour, eastern section of Granton Harbour]
-
A.
hasNearbyHarbor
Indicates that one location has a harbor situated close to it in geographic proximity.
-
B.
hasHarbourEntrance
Indicates that an entity serves as the entrance or access point to a harbour for another entity.
-
C.
locatedInHarbourArea
chosen
Indicates that something is situated within the geographic or administrative boundaries of a harbour area.
-
D.
harbourSide
Indicates a location or object that is situated alongside or directly adjacent to a harbour.
-
E.
hasHarbor
Indicates that a place possesses or contains a harbor for docking or sheltering vessels.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffc89596d08190b97bd60b45c7f9c0 |
completed | May 9, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69ffc81ba5dc8190ae94d44e2284948f |
completed | May 9, 2026, 11:49 p.m. |
Created at: May 3, 2026, 4:32 p.m.