Triple
T11883977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaucer the pilgrim |
E282728
|
entity |
| Predicate | travelsRoute |
P79601
|
FINISHED |
| Object | from Southwark to Canterbury |
—
|
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: from Southwark to Canterbury | Statement: [Chaucer the pilgrim, travelsRoute, from Southwark to Canterbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelsRoute Context triple: [Chaucer the pilgrim, travelsRoute, from Southwark to Canterbury]
-
A.
travelRouteOf
chosen
Indicates the path or itinerary that an entity follows or uses when traveling from one location to another.
-
B.
travelsDirection
Indicates that an entity moves or is transported in a specified directional heading or orientation.
-
C.
travelsThrough
Indicates that something moves along, passes across, or is routed via a particular path, medium, or location.
-
D.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
E.
travelsOn
Indicates that an entity moves or journeys using a particular route, path, or mode of transportation.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a02ad4819090faef0e0be732ee |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.