Triple
T26160585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madhavdev College |
E660096
|
entity |
| Predicate | hasNamesakeReligion |
P173237
|
FINISHED |
| Object | Hinduism |
—
|
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: Hinduism | Statement: [Madhavdev College, hasNamesakeReligion, Hinduism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamesakeReligion Context triple: [Madhavdev College, hasNamesakeReligion, Hinduism]
-
A.
hasEponymReligion
Indicates that a religion is named after or derived from the name of a particular person.
-
B.
hasNameInReligionOrFolklore
Indicates that an entity is known by a particular name specifically within a religious or folkloric tradition.
-
C.
hasReligiousName
Indicates that an entity possesses a name specifically associated with a religious context, role, or tradition.
-
D.
namedForPersonReligion
chosen
Indicates that something is named after a person specifically because of that person's religious identity, role, or significance.
-
E.
hasReligiousAffiliationInName
Indicates that an entity’s name explicitly includes or reflects a religious affiliation or association.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 26, 2026, 8:30 p.m.