Triple
T35204484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watford, Northamptonshire |
E1016495
|
entity |
| Predicate | hasNearbyHistoricalRoute |
P115769
|
FINISHED |
| Object | Roman road Watling Street (A5) |
—
|
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: Roman road Watling Street (A5) | Statement: [Watford, Northamptonshire, hasNearbyHistoricalRoute, Roman road Watling Street (A5)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHistoricalRoute Context triple: [Watford, Northamptonshire, hasNearbyHistoricalRoute, Roman road Watling Street (A5)]
-
A.
nearHistoricalRoute
chosen
Indicates that one entity is located close to a historically significant route or pathway.
-
B.
hasHistoricalRoute
Indicates that an entity possesses or is associated with a route that has historical significance or origin.
-
C.
historicalRouteVia
Indicates that a historical route or path passed through or was connected by a particular intermediate location or segment.
-
D.
nearbyHistoricalFunction
Indicates that one entity is located close to another entity that has or had a historical role, use, or function.
-
E.
nearbyHistoricalServiceFor
Indicates that a historical service or facility is located close to a given reference entity or location.
- 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0004582bb08190b8d0b88251e8d333 |
completed | May 10, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a0003e3e5588190933beea5fb28f150 |
completed | May 10, 2026, 4:04 a.m. |
Created at: May 3, 2026, 4:02 p.m.