Triple
T2853313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria Harbour |
E63140
|
entity |
| Predicate | hasAverageTidalRange |
P4652
|
FINISHED |
| Object | about 2 metres |
—
|
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: about 2 metres | Statement: [Victoria Harbour, hasAverageTidalRange, about 2 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAverageTidalRange Context triple: [Victoria Harbour, hasAverageTidalRange, about 2 metres]
-
A.
hasTidalRange
chosen
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
-
B.
hasIslandAtMouth
Indicates that a geographic feature, typically a river, has an island located at or near its mouth where it meets a larger body of water.
-
C.
hasNotableSea
Indicates that an entity is associated with or contains a sea that is considered notable or significant.
-
D.
hasEstuaryNear
Indicates that the estuary of a water body is located in close proximity to a specified place or feature.
-
E.
isTidal
Indicates that something is influenced or driven by tidal forces or tidal movements.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf5f21348190a574fa86bc71c76f |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd10aef88190b750aae07e7df4dc |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.