Triple
T34933973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandaeans in Iran |
E1007516
|
entity |
| Predicate | baptismSetting |
P147141
|
FINISHED |
| Object | flowing natural water |
—
|
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: flowing natural water | Statement: [Mandaeans in Iran, baptismSetting, flowing natural water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baptismSetting Context triple: [Mandaeans in Iran, baptismSetting, flowing natural water]
-
A.
baptismPlace
Indicates the place where an individual was baptized.
-
B.
baptismAssociatedWith
chosen
Indicates a relationship in which an entity is connected or related to a baptism event, such as by participation, performance, location, or contextual association.
-
C.
baptismEvent
Indicates an event in which a person undergoes the religious rite of baptism, typically involving a ceremonial use of water to mark initiation or purification.
-
D.
practicesBaptismType
Indicates that an entity performs or follows a specific type or form of baptism as part of its religious practice.
-
E.
baptismCountry
Indicates the country in which an entity’s baptism took place.
- 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.