Triple
T36403494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple Cave |
E896690
|
entity |
| Predicate | isMajorSiteDuring |
P14730
|
FINISHED |
| Object | Thaipusam festival |
—
|
NE NERFINISHED |
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: Thaipusam festival | Statement: [Temple Cave, isMajorSiteDuring, Thaipusam festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorSiteDuring Context triple: [Temple Cave, isMajorSiteDuring, Thaipusam festival]
-
A.
isMajorFor
Indicates that one entity serves as the primary field of academic specialization (major) for another entity, typically a student.
-
B.
isMajor
chosen
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
C.
isMajorSeeWithin
Indicates that one entity is the primary or most significant location or area encompassed within the boundaries of another entity.
-
D.
isMajorEvent
Indicates that an event is of significant importance, scale, or impact compared to typical or minor events.
-
E.
isMajorDelegateDay
Indicates that a given day is designated as a primary or significant day for delegate-related activities or responsibilities.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:10 p.m.