Triple
T6978374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Rothay |
E161772
|
entity |
| Predicate | crossesRoad |
P33132
|
FINISHED |
| Object | A591 road |
—
|
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: A591 road | Statement: [River Rothay, crossesRoad, A591 road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesRoad Context triple: [River Rothay, crossesRoad, A591 road]
-
A.
crossesStreet
Indicates that an entity moves from one side of a street to the other, traversing the street’s width.
-
B.
mainRoadCrossingBetween
Indicates that a primary or main road intersects or passes between two specified locations or entities.
-
C.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
D.
crossedByHighway
chosen
Indicates that a highway passes across or through the extent of a given entity or area.
-
E.
crossesBetween
Indicates that one entity passes from one side of a second entity to the other, traversing the space between two reference points or boundaries associated with that second entity.
- F. None of above.
Provenance (3 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_69c68854a0d88190bc0bf82263f1afce |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db68d25c8190a1776908619ad979 |
completed | March 27, 2026, 7:32 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c262508190a7708b3d9cf23d7c |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:31 p.m.