Triple
T2909473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Journey Behind the Falls |
E63646
|
entity |
| Predicate | viewingDistanceFromFalls |
P42842
|
FINISHED |
| Object | very close proximity |
—
|
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: very close proximity | Statement: [Journey Behind the Falls, viewingDistanceFromFalls, very close proximity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewingDistanceFromFalls Context triple: [Journey Behind the Falls, viewingDistanceFromFalls, very close proximity]
-
A.
distanceFallen
Indicates the amount of vertical distance an object has moved downward from its starting point due to falling.
-
B.
hasScenicViewOf
Indicates that one entity offers a visually appealing or picturesque view of another entity.
-
C.
landingDistance
Indicates the required or actual distance needed for an aircraft or object to complete a landing from approach to full stop.
-
D.
depthMetresApprox
Indicates an approximate measurement of how deep something is in metres, rather than an exact value.
-
E.
fallsIn
Indicates that one entity is located within, contained by, or geographically/administratively included inside another entity.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0d329c88190b6fcaef0be1799eb |
completed | March 7, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69abdd1b77608190b20fc078fdb85e64 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddedd72c819094a9c4161af07780 |
completed | March 7, 2026, 8:12 a.m. |
Created at: March 6, 2026, 10:11 p.m.