Triple
T32825018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banjar culture |
E839532
|
entity |
| Predicate | festiveEvent |
P134250
|
FINISHED |
| Object | Maulid Nabi celebrations |
—
|
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: Maulid Nabi celebrations | Statement: [Banjar culture, festiveEvent, Maulid Nabi celebrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festiveEvent Context triple: [Banjar culture, festiveEvent, Maulid Nabi celebrations]
-
A.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
B.
celebrationAssociatedWith
chosen
Indicates a relationship where a celebration is connected to, linked with, or held in relation to a particular entity, event, or context.
-
C.
festivalFunction
Indicates that an event serves as a festival or is functioning in the role of a festival within a given context.
-
D.
festivalActivity
Indicates that an entity is an event, performance, or engagement that takes place as part of a festival’s organized program.
-
E.
isCelebratoryOf
Indicates that something expresses celebration, honor, or festive recognition directed toward a particular event, person, or occasion.
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:15 a.m.