Triple
T12749404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poy Sang Long festival |
E304689
|
entity |
| Predicate | processionFeature |
P6086
|
FINISHED |
| Object | boys carried on shoulders of male relatives |
—
|
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: boys carried on shoulders of male relatives | Statement: [Poy Sang Long festival, processionFeature, boys carried on shoulders of male relatives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processionFeature Context triple: [Poy Sang Long festival, processionFeature, boys carried on shoulders of male relatives]
-
A.
ceremonialProcession
chosen
Indicates a formal, often ritualized movement of people or objects in an organized sequence as part of a ceremony or official event.
-
B.
associatedDeityProcession
Indicates that a deity is linked to, honored by, or represented in a particular procession or ceremonial parade.
-
C.
mainProcessionDay
Indicates the specific day on which the primary or central procession of an event or celebration takes place.
-
D.
locationOfProcessions
Indicates the place where processions occur or are held.
-
E.
processionStartingPoint
Indicates the location or entity where a procession begins or is initiated.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:27 p.m.