Triple
T11883955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaucer the pilgrim |
E282728
|
entity |
| Predicate | journeyPurpose |
P102055
|
FINISHED |
| Object | pilgrimage to the shrine of Thomas Becket |
—
|
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: pilgrimage to the shrine of Thomas Becket | Statement: [Chaucer the pilgrim, journeyPurpose, pilgrimage to the shrine of Thomas Becket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: journeyPurpose Context triple: [Chaucer the pilgrim, journeyPurpose, pilgrimage to the shrine of Thomas Becket]
-
A.
typicalJourneyPurpose
Indicates the usual or most common reason or objective for which an entity undertakes a journey.
-
B.
sunJourneyPurpose
Indicates the purpose or intended goal behind a sun-related journey or movement.
-
C.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
D.
journeyFrom
Indicates that an entity undertakes or originates a journey starting from a specified location or source.
-
E.
explorationPurpose
Indicates that an entity is engaged in or associated with an activity whose primary goal is exploration or discovery.
- 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_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. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:44 p.m.