Triple
T34383828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marsa |
E882505
|
entity |
| Predicate | hasHarbourFront |
P3007
|
FINISHED |
| Object | Grand Harbour waterfront |
—
|
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: Grand Harbour waterfront | Statement: [Marsa, hasHarbourFront, Grand Harbour waterfront]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHarbourFront Context triple: [Marsa, hasHarbourFront, Grand Harbour waterfront]
-
A.
hasHarbourEntrance
Indicates that an entity serves as the entrance or access point to a harbour for another entity.
-
B.
hasHarbor
chosen
Indicates that a place possesses or contains a harbor for docking or sheltering vessels.
-
C.
hasAncestralHarbour
Indicates that an entity has a harbour that historically served as the origin or ancestral port associated with it.
-
D.
hasHarborCity
Indicates that one entity possesses or is associated with a city that functions as its harbor or port.
-
E.
hasNearbyHarbor
Indicates that one location has a harbor situated close to it in geographic proximity.
- 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 1:59 a.m.