Triple
T36894020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | shrine to Jobu |
E911837
|
entity |
| Predicate | inspiredSportsRituals |
P194338
|
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: [shrine to Jobu, inspiredSportsRituals, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredSportsRituals Context triple: [shrine to Jobu, inspiredSportsRituals, yes]
-
A.
ritualActivities
Indicates that one entity engages in, performs, or is associated with ritualistic or ceremonial activities in relation to another entity or context.
-
B.
ritualsDirectedAt
Indicates that certain rituals are performed with a specific entity, object, or target as their intended focus or recipient.
-
C.
ritualSignificance
Indicates that something holds special importance or meaning within a ritual or ceremonial context.
-
D.
inspiredRealWorldSport
Indicates that one entity served as the real-world sport that influenced or inspired the creation, design, or concept of another entity.
-
E.
ritualCategory
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
- 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
| PDg | Predicate description generation | batch_69fd6a1a38f081908c573aee4696de4f |
completed | May 8, 2026, 4:44 a.m. |
Created at: May 3, 2026, 4:13 p.m.