Triple
T38107791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roger of Ware |
E951569
|
entity |
| Predicate | pilgrimGroup |
P100394
|
FINISHED |
| Object | Canterbury pilgrims |
—
|
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: Canterbury pilgrims | Statement: [Roger of Ware, pilgrimGroup, Canterbury pilgrims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilgrimGroup Context triple: [Roger of Ware, pilgrimGroup, Canterbury pilgrims]
-
A.
pilgrimsFrom
Indicates that one or more pilgrims originate from, or are associated with coming from, a particular place.
-
B.
pilgrimIdentity
Indicates that an entity is identified as a pilgrim, typically in the context of undertaking or being associated with a religious or spiritual journey.
-
C.
pilgrimInfrastructure
Indicates a relationship where infrastructure is specifically designed, used, or maintained to support the needs and activities of pilgrims.
-
D.
pilgrimsObtain
Indicates that pilgrims acquire, receive, or come into possession of something.
-
E.
hasPilgrims
chosen
Indicates that an entity is associated with or contains pilgrims, typically as visitors, members, or participants in a pilgrimage.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.