Triple
T23966997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reversing Falls Railway Bridge |
E604112
|
entity |
| Predicate | gorgeCrossed |
P154064
|
FINISHED |
| Object | Reversing Falls gorge |
—
|
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: Reversing Falls gorge | Statement: [Reversing Falls Railway Bridge, gorgeCrossed, Reversing Falls gorge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gorgeCrossed Context triple: [Reversing Falls Railway Bridge, gorgeCrossed, Reversing Falls gorge]
-
A.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
B.
reachedRiver
Indicates that an entity has arrived at or come into contact with a river as a result of movement or travel.
-
C.
lakeTypeCrossed
Indicates that one entity has traversed or passed across a lake of a specified type.
-
D.
crossesWatershed
Indicates that one entity passes from one drainage basin or watershed area into another, traversing the boundary between them.
-
E.
containsGorge
Indicates that one entity geographically includes or encompasses a gorge within its area or boundaries.
- 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.