Triple
T31871796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agaunum |
E813621
|
entity |
| Predicate | pilgrimageBeganInCentury |
P150682
|
FINISHED |
| Object | 5th 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: 5th century | Statement: [Agaunum, pilgrimageBeganInCentury, 5th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilgrimageBeganInCentury Context triple: [Agaunum, pilgrimageBeganInCentury, 5th century]
-
A.
historicalPeriodOfPilgrimage
Indicates the historical period during which a given pilgrimage took place or was practiced.
-
B.
foundedAsReligiousSiteInCentury
Indicates that something was originally established as a religious site during a specified century.
-
C.
pilgrimageSince
Indicates that an entity has been engaged in or committed to a pilgrimage starting from a specified point in time.
-
D.
pilgrimageAssociatedWith
Indicates a relationship where a pilgrimage is connected or related to a particular entity, such as a place, person, event, or religious tradition.
-
E.
wasPilgrimageCenterIn
chosen
Indicates that a place functioned as a pilgrimage center in a specified time or period.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 11:54 p.m.