Triple
T8390056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puckeridge |
E197918
|
entity |
| Predicate | historicallyOnRoute |
P12633
|
FINISHED |
| Object | London to Cambridge coaching route |
—
|
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: London to Cambridge coaching route | Statement: [Puckeridge, historicallyOnRoute, London to Cambridge coaching route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyOnRoute Context triple: [Puckeridge, historicallyOnRoute, London to Cambridge coaching route]
-
A.
hasHistoricalRoute
chosen
Indicates that an entity possesses or is associated with a route that has historical significance or origin.
-
B.
historicRoute
Indicates that a route has historical significance, typically due to its age, past usage, or role in notable events.
-
C.
historicalPass
Indicates that an entity has successfully completed or passed a historical event, period, or examination related to history.
-
D.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
E.
hasHistoricStreet
Indicates that an entity is associated with or located on a street that has recognized historical significance.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb810ac380819095bd67f0555ac2a8 |
completed | March 31, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:03 p.m.