Triple
T3197560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madras High Court |
E66969
|
entity |
| Predicate | MaduraiBenchEstablishedOn |
P41
|
FINISHED |
| Object | 2004-07-24 |
—
|
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: 2004-07-24 | Statement: [Madras High Court, MaduraiBenchEstablishedOn, 2004-07-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MaduraiBenchEstablishedOn Context triple: [Madras High Court, MaduraiBenchEstablishedOn, 2004-07-24]
-
A.
foundedOnSiteOf
Indicates that something was established or built at the same physical location where another, earlier entity or structure previously existed.
-
B.
ashramEstablishedFor
Indicates that an ashram was founded or set up specifically for the benefit, use, or purpose of a particular person, group, or cause.
-
C.
foundedOn
chosen
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
-
D.
foundedCityOnSiteOf
Indicates that a city was established on the same physical location where another settlement or city previously existed.
-
E.
festivalFounded
Indicates that a particular festival was established or created by a specific person, group, or organization.
- 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_69ad8588ba18819086a10951c32ecb80 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada7192994819084817307065a25e2 |
completed | March 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69ad9e05e4f48190adbe4366cdba2349 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.