Triple
T23365378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Duthac |
E593301
|
entity |
| Predicate | shrineStatus |
P146312
|
FINISHED |
| Object | important pilgrimage destination in medieval Scotland |
—
|
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: important pilgrimage destination in medieval Scotland | Statement: [Saint Duthac, shrineStatus, important pilgrimage destination in medieval Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shrineStatus Context triple: [Saint Duthac, shrineStatus, important pilgrimage destination in medieval Scotland]
-
A.
stateShrineOf
Indicates that one entity is officially designated as a state-recognized shrine associated with or located within another entity (typically a state or region).
-
B.
shrineRank
Indicates the hierarchical or status level assigned to a shrine relative to other shrines.
-
C.
shrineType
Indicates the specific category or kind of shrine associated with an entity.
-
D.
shrineSignificance
chosen
Indicates the cultural, religious, or historical importance attributed to a particular shrine within its context.
-
E.
shrineName
Indicates that an entity has the specified name of a shrine.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0ab7fc481908b496ec9b543eddd |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:31 p.m.