Triple
T476922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Druze |
E9081
|
entity |
| Predicate | prohibitsConversionIn |
P12540
|
FINISHED |
| Object | both directions |
—
|
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: both directions | Statement: [Druze, prohibitsConversionIn, both directions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prohibitsConversionIn Context triple: [Druze, prohibitsConversionIn, both directions]
-
A.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
B.
doesNotAllow
chosen
Indicates that one entity prevents, forbids, or does not permit another entity from performing a specific action or being in a certain state.
-
C.
convertsTo
Indicates that one entity is transformed or changed into another entity, typically resulting in a different state, form, or representation.
-
D.
cannotBeAmendedInRespectOf
Indicates that a particular item (such as a term, provision, or condition) is not allowed to be changed or modified in the specified respect or aspect.
-
E.
notableRestriction
Indicates that there is a significant limitation, constraint, or prohibition that meaningfully affects the entity or its use.
- 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_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. |
Created at: Feb. 28, 2026, 1:12 p.m.