Triple
T23967001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reversing Falls Railway Bridge |
E604112
|
entity |
| Predicate | hasTurbulentWatersBelow |
P154065
|
FINISHED |
| Object | Reversing Falls rapids |
—
|
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: Reversing Falls rapids | Statement: [Reversing Falls Railway Bridge, hasTurbulentWatersBelow, Reversing Falls rapids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTurbulentWatersBelow Context triple: [Reversing Falls Railway Bridge, hasTurbulentWatersBelow, Reversing Falls rapids]
-
A.
hasClearanceAboveWater
Indicates that one entity is positioned or maintained at a height safely above the water level.
-
B.
hasRiverBelow
Indicates that one entity is located above another such that a river lies physically below it.
-
C.
hasShelteredWaters
Indicates that one location provides protected or calm waters for another location or activity, shielding it from rough or open conditions.
-
D.
hasGorgeBelow
Indicates that one entity is situated above another entity such that a gorge lies directly below it.
-
E.
hasSeaCondition
Indicates that an entity is associated with or characterized by a particular state or condition of the sea.
- F. None of above. chosen
Provenance (4 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1d7fbf88190820bcfbdc237c2a3 |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:24 p.m.