Triple
T34144276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camino Inglés |
E875804
|
entity |
| Predicate | compostelaEligibility |
P194819
|
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, compostelaEligibility, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compostelaEligibility Context triple: [Camino Inglés, compostelaEligibility, yes]
-
A.
qualifyingFor
Indicates that one entity meets the necessary conditions or criteria to be eligible for another entity, status, or action.
-
B.
eligibleThrough
Indicates that one entity qualifies for or gains eligibility to something by means of, or as a result of, another specified entity, condition, or process.
-
C.
positionEligible
Indicates that an entity is qualified or permitted to hold or be assigned to a particular position or role.
-
D.
eligibleFrom
Indicates that a subject becomes or is considered eligible starting from a specified point in time or condition.
-
E.
branchEligibility
Indicates whether an entity meets the conditions required to qualify for a particular branch, option, or subdivision within a larger system or structure.
- F. None of above. chosen
Provenance (4 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_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
| PDg | Predicate description generation | batch_69fd884b9d908190833de9500ff6d62a |
completed | May 8, 2026, 6:52 a.m. |
Created at: May 1, 2026, 1:54 a.m.