Triple
T8614737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vandiyur Mariamman Teppakulam |
E204006
|
entity |
| Predicate | lightingDuringFestival |
P31011
|
FINISHED |
| Object | oil lamps |
—
|
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: oil lamps | Statement: [Vandiyur Mariamman Teppakulam, lightingDuringFestival, oil lamps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightingDuringFestival Context triple: [Vandiyur Mariamman Teppakulam, lightingDuringFestival, oil lamps]
-
A.
hasNightRaceLighting
Indicates that the subject facility or venue is equipped with lighting suitable for hosting events or activities at night.
-
B.
hasLightShow
chosen
Indicates that an entity features or presents a light-based visual display or performance.
-
C.
lightingPractice
Indicates a relationship where an entity engages in or performs activities to rehearse, refine, or experiment with lighting setups or techniques.
-
D.
illuminationCondition
Indicates the lighting or brightness conditions under which an event, observation, or interaction takes place.
-
E.
festivalDay
Indicates that a given day is designated as a festival or celebration day within a particular context or calendar.
- 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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc47020748819090f658c115c1a7b9 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.