Triple
T36743128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Thames between Staines and Egham |
E907674
|
entity |
| Predicate | downstreamTerminusNear |
P186257
|
FINISHED |
| Object | Runnymede area near Egham |
—
|
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: Runnymede area near Egham | Statement: [River Thames between Staines and Egham, downstreamTerminusNear, Runnymede area near Egham]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: downstreamTerminusNear Context triple: [River Thames between Staines and Egham, downstreamTerminusNear, Runnymede area near Egham]
-
A.
nearbyTerminus
Indicates that one terminus (end point or final stop) is located close to another terminus in space.
-
B.
easternTerminusNearby
Indicates that the eastern endpoint of one entity is located close to the referenced entity.
-
C.
downstreamBoundary
Indicates that one entity serves as the downstream limit or endpoint of another entity’s flow, process, or influence.
-
D.
terminusSouthNear
Indicates that the southern end or terminus of one entity is located close to another entity.
-
E.
distanceFromTerminus
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
- 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_69f76e76d10881909ec1679bc043108c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabacc1481909e839454ce1057f7 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7c9f4c7c48190ba918d8d5dc8dfd9 |
completed | May 3, 2026, 10:19 p.m. |
Created at: May 3, 2026, 4:12 p.m.