Triple
T476923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Druze |
E9081
|
entity |
| Predicate | allowsConversionTo |
P14329
|
FINISHED |
| Object | no other religion |
—
|
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: no other religion | Statement: [Druze, allowsConversionTo, no other religion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsConversionTo Context triple: [Druze, allowsConversionTo, no other religion]
-
A.
convertsTo
Indicates that one entity is transformed or changed into another entity, typically resulting in a different state, form, or representation.
-
B.
convertsFrom
Indicates that one entity is transformed or changed into another entity, with the source being the starting form or state.
-
C.
convertedFrom
Indicates that one entity has been transformed or changed in form, type, or representation from another entity.
-
D.
canAlsoBe
Indicates that something has an additional possible state, role, or classification beyond its primary one.
-
E.
conversionEvent
Indicates that a user or entity has completed a desired target action (such as a purchase, signup, or other goal) that counts as a successful conversion.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f03cc63881908e75b457804cb858 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf017548190ae38ff3314a1ffa3 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef06d2fc8190b379d575215a8518 |
completed | Feb. 28, 2026, 1:35 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.