Triple
T18614739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hangzhou Bay Bridge |
E454988
|
entity |
| Predicate | hasTidalEnvironment |
P57287
|
FINISHED |
| Object | strong tidal currents |
—
|
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: strong tidal currents | Statement: [Hangzhou Bay Bridge, hasTidalEnvironment, strong tidal currents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTidalEnvironment Context triple: [Hangzhou Bay Bridge, hasTidalEnvironment, strong tidal currents]
-
A.
containsTidalFeatures
chosen
Indicates that one entity exhibits observable tidal features caused by gravitational interactions with another entity.
-
B.
hasTidalRange
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
-
C.
hasTidalConnection
Indicates that one entity is linked to another through the movement, influence, or exchange of tidal waters.
-
D.
hasTidalConstituent
Indicates that something includes or is associated with a specific tidal constituent as part of its tidal characteristics or behavior.
-
E.
hasMarineHabitatType
Indicates that an entity is associated with or occurs in a specific type of marine habitat.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d03feb88190bbd8889273d82f7f |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.