Triple
T32639143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Santo Sepulcro |
E834431
|
entity |
| Predicate | isInTownOnRoute |
P6309
|
FINISHED |
| Object | Estella on the Camino Francés |
—
|
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: Estella on the Camino Francés | Statement: [Church of Santo Sepulcro, isInTownOnRoute, Estella on the Camino Francés]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInTownOnRoute Context triple: [Church of Santo Sepulcro, isInTownOnRoute, Estella on the Camino Francés]
-
A.
locatedOnRouteTo
Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
-
B.
isPartOfRoute
chosen
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
C.
isOnIslandRoute
Indicates that something (such as a path, trip, or connection) follows a route that involves traveling to, from, or around an island.
-
D.
isTrailTownFor
Indicates that a town serves as a designated support or access point for a particular trail or route.
-
E.
isInCity
Indicates that one entity is located within the geographical boundaries of a specified city.
- 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c775d6188190b236fc4f89a11b61 |
completed | May 3, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:07 a.m.