Triple
T25283710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | shibi (Qiang ritual specialist) |
E633880
|
entity |
| Predicate | performsAtOccasion |
P125499
|
FINISHED |
| Object | festivals |
—
|
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: festivals | Statement: [shibi (Qiang ritual specialist), performsAtOccasion, festivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsAtOccasion Context triple: [shibi (Qiang ritual specialist), performsAtOccasion, festivals]
-
A.
onOccasionOf
Indicates that one event, action, or state occurs in connection with, or is triggered by, a particular occasion or special event.
-
B.
typicalPerformanceOccasion
chosen
Indicates the usual or characteristic type of occasion, event, or context in which a performance typically takes place.
-
C.
createdOnOccasionOf
Indicates that something was created specifically for, or in direct connection with, a particular event, occasion, or circumstance.
-
D.
entryOccasion
Indicates the circumstance, event, or reason that prompts or justifies an entity’s entry or initiation.
-
E.
targetOccasion
Indicates the specific event, situation, or occasion toward which an action, plan, or intention is directed.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 1:19 p.m.