Triple
T26200366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harappan religion |
E655211
|
entity |
| Predicate | worshipPlaceHypothesis |
P164823
|
FINISHED |
| Object | household shrines |
—
|
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: household shrines | Statement: [Harappan religion, worshipPlaceHypothesis, household shrines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipPlaceHypothesis Context triple: [Harappan religion, worshipPlaceHypothesis, household shrines]
-
A.
hasPlaceOfWorship
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
-
B.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
C.
isInUseForWorship
Indicates that something is currently being used for religious or worship-related activities.
-
D.
countryOfWorshipSite
Indicates that a place of worship is located within the borders of a specified country.
-
E.
religiousHouse
Indicates that an entity is a religious institution or building used for worship, residence, or activities of a religious community.
- F. None of above. chosen
Provenance (4 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 26, 2026, 8:48 p.m.