Triple
T11573361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaro Fiesta |
E274443
|
entity |
| Predicate | hasPilgrims |
P100394
|
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: [Jaro Fiesta, hasPilgrims, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPilgrims Context triple: [Jaro Fiesta, hasPilgrims, yes]
-
A.
pilgrimsFrom
Indicates that one or more pilgrims originate from, or are associated with coming from, a particular place.
-
B.
pilgrimFootfall
Indicates the occurrence or trace of a pilgrim’s steps or movement along a path or at a specific place.
-
C.
primaryPilgrims
Indicates that the referenced entities are the main or principal participants undertaking a pilgrimage in relation to something or someone.
-
D.
hasPilgrimagePeak
Indicates that a place or route is associated with a specific peak that serves as a destination or focal point for religious or spiritual pilgrimage.
-
E.
hasPilgrimageFunctionSince
Indicates that an entity has served a pilgrimage-related role or function continuously since a specified point in time.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89048120c81908258f984711f7dd4 |
completed | April 10, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.