Triple
T2254025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M73 motorway |
E49678
|
entity |
| Predicate | runsAlongSide |
P31095
|
FINISHED |
| Object | eastern side of Glasgow |
—
|
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: eastern side of Glasgow | Statement: [M73 motorway, runsAlongSide, eastern side of Glasgow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsAlongSide Context triple: [M73 motorway, runsAlongSide, eastern side of Glasgow]
-
A.
operatedAlongside
Indicates that two or more entities functioned or were active together in a coordinated or concurrent manner within the same context or system.
-
B.
runsAcross
Indicates that one entity moves quickly on foot from one side of another entity, area, or boundary to the opposite side, traversing it in a roughly straight path.
-
C.
situatedOnSideOf
chosen
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
D.
appearsAlongside
Indicates that two entities are present or occur together in the same context, setting, or instance.
-
E.
runsDirectlyOver
Indicates that one entity passes or extends immediately above another along its length or span, without significant vertical separation or intervening structures.
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc12029548190af9f2cdd7a4de2d6 |
completed | March 7, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.