Triple
T34503914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vivaha Panchami |
E885830
|
entity |
| Predicate | majorCelebrationPlace |
P7822
|
FINISHED |
| Object | Janakpur |
—
|
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: Janakpur | Statement: [Vivaha Panchami, majorCelebrationPlace, Janakpur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCelebrationPlace Context triple: [Vivaha Panchami, majorCelebrationPlace, Janakpur]
-
A.
significantEventPlace
Indicates the place where a significant event occurred or is associated with an entity.
-
B.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
C.
capitalOfCelebration
Indicates that a location is recognized as the primary or central place where a particular celebration or festivity is most prominently held or symbolically based.
-
D.
isMostFamouslyObservedIn
Indicates that something is best known or primarily recognized for being observed or occurring in a particular place, context, or setting.
-
E.
isCelebratedIn
chosen
Indicates that an event, person, or occasion is honored, observed, or commemorated within a particular place, time, or context.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
Created at: May 1, 2026, 2:01 a.m.