Triple
T28763958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A3 road |
E726202
|
entity |
| Predicate | northernTownConnected |
P165786
|
FINISHED |
| Object | Ramsey |
—
|
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: Ramsey | Statement: [A3 road, northernTownConnected, Ramsey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: northernTownConnected Context triple: [A3 road, northernTownConnected, Ramsey]
-
A.
northernConnection
Indicates a relationship where one entity is connected to another primarily through or via its northern side, direction, or region.
-
B.
connectsNorthTo
Indicates that one entity serves as a connection or link from another entity to something located to its north.
-
C.
northernTerminusConnects
Indicates that a route, line, or pathway connects to or ends at a specified location at its northernmost terminus.
-
D.
northernExtensionLocatedIn
Indicates that the northern extension or northernmost part of one entity is geographically located within the area or boundaries of another entity.
-
E.
northernTerminusCity
Indicates that one city serves as the northern endpoint or final stop of a route, line, or corridor relative to another location.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a6babcc81908052c9907a99c882 |
completed | May 2, 2026, 8:11 p.m. |
Created at: April 28, 2026, 6:12 a.m.