Triple
T32639020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Way |
E834428
|
entity |
| Predicate | requiresPilgrimPassportForCompostela |
P91814
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [French Way, requiresPilgrimPassportForCompostela, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPilgrimPassportForCompostela Context triple: [French Way, requiresPilgrimPassportForCompostela, yes]
-
A.
compostelaEligibility
Indicates whether an entity meets the conditions required to be eligible for receiving the Compostela.
-
B.
pilgrimageObligationAppliesTo
Indicates that the duty or requirement to perform a pilgrimage applies to a particular entity.
-
C.
requiresPassport
chosen
Indicates that access to or participation in something is conditional on possessing a valid passport.
-
D.
requiresJourneyOf
Indicates that one entity can only be achieved, accessed, or completed by undertaking a journey or progression involving another entity.
-
E.
hasPilgrimageFrom
Indicates that a pilgrimage originates from or is undertaken starting at a specified location or source.
- 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_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: May 1, 2026, 1:07 a.m.