Triple
T34585219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patel: A Life |
E888023
|
entity |
| Predicate | hasBiographicalSubjectReligion |
P27867
|
FINISHED |
| Object | Hinduism |
—
|
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: Hinduism | Statement: [Patel: A Life, hasBiographicalSubjectReligion, Hinduism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBiographicalSubjectReligion Context triple: [Patel: A Life, hasBiographicalSubjectReligion, Hinduism]
-
A.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
B.
hasReligiousCharacter
Indicates that an entity possesses a religious nature, function, or affiliation, or is characterized by religious aspects or significance.
-
C.
hasEponymReligion
Indicates that a religion is named after or derived from the name of a particular person.
-
D.
hasAssociatedReligion
chosen
Indicates that an entity is connected with or linked to a particular religion.
-
E.
namedForPersonReligion
Indicates that something is named after a person specifically because of that person's religious identity, role, or significance.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 1, 2026, 2:03 a.m.