Triple
T26496607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Podiensis |
E669297
|
entity |
| Predicate | notableSiteOnRoute |
P78460
|
FINISHED |
| Object | Sainte-Foy Abbey Church in Conques |
—
|
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: Sainte-Foy Abbey Church in Conques | Statement: [Via Podiensis, notableSiteOnRoute, Sainte-Foy Abbey Church in Conques]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSiteOnRoute Context triple: [Via Podiensis, notableSiteOnRoute, Sainte-Foy Abbey Church in Conques]
-
A.
notableSiteListedOn
Indicates that a notable site is recorded or referenced within a particular list, registry, or catalog.
-
B.
notableSite
Indicates that a site holds particular significance, prominence, or recognition in some context.
-
C.
notableSiteAssociatedWith
chosen
Indicates that there is a significant or noteworthy site or location that is associated with, related to, or prominently linked to the given entity.
-
D.
notableSiteFor
Indicates that a site is particularly recognized or distinguished for a specific feature, activity, event, or characteristic.
-
E.
notableSpot
Indicates that a location is recognized as a significant or noteworthy place in some context.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
Created at: April 27, 2026, 1:09 a.m.