Triple
T26099652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vauxhall End stands |
E658360
|
entity |
| Predicate | locatedAtEnd |
P43881
|
FINISHED |
| Object | Vauxhall End |
—
|
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: Vauxhall End | Statement: [Vauxhall End stands, locatedAtEnd, Vauxhall End]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtEnd Context triple: [Vauxhall End stands, locatedAtEnd, Vauxhall End]
-
A.
alignmentAtEnd
Indicates that two or more elements share a common alignment specifically at their ending boundary or edge.
-
B.
locatedAtTipOf
Indicates that one entity is positioned at the extreme end or tip of another entity.
-
C.
locatedAtTerminusOf
chosen
Indicates that one entity is situated at the end point or final terminus of another entity, such as a route, line, or path.
-
D.
locatedAtInteractionPoint
Indicates that an entity is positioned at a specific interaction point where interactions or exchanges are intended to occur.
-
E.
locatedAfter
Indicates that one entity is positioned later than another along a defined sequence, order, or spatial/temporal axis.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 26, 2026, 7:53 p.m.