Triple
T2871524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gangaur |
E63572
|
entity |
| Predicate | associatedRitualObject |
P7123
|
FINISHED |
| Object | earthen pots |
—
|
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: earthen pots | Statement: [Gangaur, associatedRitualObject, earthen pots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRitualObject Context triple: [Gangaur, associatedRitualObject, earthen pots]
-
A.
hasRitualObject
chosen
Indicates that an entity possesses, uses, or is associated with an object specifically employed in a ritual or ceremonial context.
-
B.
appearsInRitual
Indicates that an entity is included, featured, or participates as a component or element within a specific ritual.
-
C.
partOfRitual
Indicates that an action, object, or event is included as a component or step within a larger ritual.
-
D.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
E.
hasRitualElements
Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfe46a1c819084399a191f0dfe9c |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.