Triple
T32590942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giant Gate Falls |
E833061
|
entity |
| Predicate | approxDistanceFromGladeWharf |
P197911
|
FINISHED |
| Object | about 2–3 hours walk |
—
|
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: about 2–3 hours walk | Statement: [Giant Gate Falls, approxDistanceFromGladeWharf, about 2–3 hours walk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxDistanceFromGladeWharf Context triple: [Giant Gate Falls, approxDistanceFromGladeWharf, about 2–3 hours walk]
-
A.
approxDistanceFromThames
Indicates that one entity is located at an approximate distance from the River Thames.
-
B.
distanceFromAvalon
Indicates the spatial distance separating an entity from the reference location Avalon.
-
C.
distanceFromTywynWharf
Indicates the measured distance between a given location and Tywyn Wharf.
-
D.
approxDistanceInKilometersFromWandoorJetty
Indicates an approximate distance, measured in kilometers, between a subject entity and the Wandoor Jetty location.
-
E.
distanceFromRydePierHead
Indicates the measured distance between a given location and Ryde Pier Head.
- 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
| PDg | Predicate description generation | batch_69feb8e6ed7881908446745c89c30784 |
completed | May 9, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:05 a.m.