Triple
T38108404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Group F of The Canterbury Tales |
E951584
|
entity |
| Predicate | hasPilgrim |
P100394
|
FINISHED |
| Object | The Squire |
—
|
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: The Squire | Statement: [Group F of The Canterbury Tales, hasPilgrim, The Squire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPilgrim Context triple: [Group F of The Canterbury Tales, hasPilgrim, The Squire]
-
A.
hasPilgrims
chosen
Indicates that an entity is associated with or contains pilgrims, typically as visitors, members, or participants in a pilgrimage.
-
B.
isPilgrimTo
Indicates that one entity travels to or visits a place as a religious or spiritual pilgrimage in relation to another entity.
-
C.
hasPilgrimType
Indicates that an entity is associated with, classified as, or characterized by a particular type or category of pilgrim.
-
D.
hasPilgrimActivity
Indicates a relationship where an entity engages in or is associated with pilgrim-related activities, such as religious journeys, visits to sacred sites, or acts of pilgrimage.
-
E.
hasPilgrimageFrom
Indicates that a pilgrimage originates from or is undertaken starting at a specified location or source.
- 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.