Triple
T13110810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Floating Harbour |
E310964
|
entity |
| Predicate | waterLevelCharacteristic |
P25274
|
FINISHED |
| Object | non-tidal |
—
|
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: non-tidal | Statement: [Floating Harbour, waterLevelCharacteristic, non-tidal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterLevelCharacteristic Context triple: [Floating Harbour, waterLevelCharacteristic, non-tidal]
-
A.
hasWaterCharacteristics
Indicates that one entity possesses qualities, properties, or behaviors characteristic of water.
-
B.
hydrologicalCharacteristic
chosen
Indicates a relationship where a hydrological feature or condition (such as water flow, level, or behavior) characterizes or describes another entity.
-
C.
waterLevelTrend
Indicates the direction and rate at which a body of water’s level is changing over time (e.g., rising, falling, or stable).
-
D.
hasWaterBodyCharacteristic
Indicates that a water body possesses a specified physical, chemical, or ecological characteristic.
-
E.
seaLevelCharacteristic
Indicates a characteristic, property, or attribute specifically related to sea level.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9817e4f408190b77c198b4157d77a |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:05 p.m.