Triple
T24656741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevelaer |
E610413
|
entity |
| Predicate | hasPilgrimageHistorySince |
P139663
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Kevelaer, hasPilgrimageHistorySince, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPilgrimageHistorySince Context triple: [Kevelaer, hasPilgrimageHistorySince, 17th century]
-
A.
hasPilgrimageFrom
Indicates that a pilgrimage originates from or is undertaken starting at a specified location or source.
-
B.
pilgrimageSince
chosen
Indicates that an entity has been engaged in or committed to a pilgrimage starting from a specified point in time.
-
C.
hasPilgrimageFunctionSince
Indicates that an entity has served a pilgrimage-related role or function continuously since a specified point in time.
-
D.
hasTourHistoryWith
Indicates that two entities have previously participated together in one or more tours or touring events.
-
E.
hasPilgrimageActivity
Indicates that an entity engages in, organizes, or is associated with a religious pilgrimage activity.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:34 a.m.