Triple
T5737552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magh Mela |
E126535
|
entity |
| Predicate | majorEventType |
P51476
|
FINISHED |
| Object | mass bathing festival |
—
|
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: mass bathing festival | Statement: [Magh Mela, majorEventType, mass bathing festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorEventType Context triple: [Magh Mela, majorEventType, mass bathing festival]
-
A.
significantEventType
chosen
Indicates the specific category or kind of major or noteworthy event associated with an entity or situation.
-
B.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
C.
majorFlashpointIn
Indicates that an event, issue, or conflict serves as a primary source of tension or confrontation within a specified larger context or setting.
-
D.
majorIssue
Indicates that something is a primary or most significant problem, concern, or obstacle in a given context.
-
E.
mainEventFor
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0255c8c308190821f968ec41c5078 |
completed | March 22, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:47 p.m.