Triple
T34144275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camino Inglés |
E875804
|
entity |
| Predicate | pilgrimCredentialAvailable |
P38481
|
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: [Camino Inglés, pilgrimCredentialAvailable, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilgrimCredentialAvailable Context triple: [Camino Inglés, pilgrimCredentialAvailable, yes]
-
A.
hasPilgrimCredentialUse
Indicates that an entity makes use of, or is associated with the use of, a pilgrim credential in the context of a journey or pilgrimage.
-
B.
pilgrimIdentity
Indicates that an entity is identified as a pilgrim, typically in the context of undertaking or being associated with a religious or spiritual journey.
-
C.
hasCredential
chosen
Indicates that an entity possesses or has been granted a specific credential, qualification, or certification.
-
D.
pilgrimStatus
Indicates the status or condition of an individual in relation to their role or journey as a pilgrim.
-
E.
isPilgrimTo
Indicates that one entity travels to or visits a place as a religious or spiritual pilgrimage in relation to another entity.
- 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_69f349aaeef08190a20e72a3fdeb7052 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.