Triple
T12948220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoroastrian fire temples |
E309822
|
entity |
| Predicate | purityRule |
P6859
|
FINISHED |
| Object | shoes removed before entry |
—
|
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: shoes removed before entry | Statement: [Zoroastrian fire temples, purityRule, shoes removed before entry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purityRule Context triple: [Zoroastrian fire temples, purityRule, shoes removed before entry]
-
A.
purity
chosen
Indicates that an entity possesses a high degree of cleanliness, integrity, or freedom from contamination, corruption, or mixed elements.
-
B.
purifiedBy
Indicates that something has been cleansed, refined, or made pure through the action or process performed by another agent or method.
-
C.
compositionRule
Indicates how multiple elements or components are combined or arranged according to a specific rule or pattern.
-
D.
sanctioningRules
Indicates the rules or conditions under which sanctions or penalties are imposed in response to certain actions or behaviors.
-
E.
usesRulesFrom
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.