Triple
T34846715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M+ Cinema |
E1004489
|
entity |
| Predicate | isLocatedOnWaterfront |
P186497
|
FINISHED |
| Object | Victoria Harbour |
—
|
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: Victoria Harbour | Statement: [M+ Cinema, isLocatedOnWaterfront, Victoria Harbour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedOnWaterfront Context triple: [M+ Cinema, isLocatedOnWaterfront, Victoria Harbour]
-
A.
hasWaterfrontLocation
chosen
Indicates that an entity is situated directly adjacent to or along a body of water, such as a sea, lake, or river.
-
B.
locatedInWaterfrontArea
Indicates that something is situated within a designated waterfront area adjacent to a body of water.
-
C.
isWaterfrontBuilding
Indicates that a building is located directly adjacent to a body of water, such as a river, lake, or ocean.
-
D.
hasWaterfrontType
Indicates that an entity is associated with a specific type or category of waterfront (e.g., oceanfront, lakefront, riverfront).
-
E.
isWaterfrontThoroughfare
Indicates that a thoroughfare (such as a road, street, or path) is located directly along or adjacent to a body of water.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4 p.m.