Triple
T27972913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islamic Penal Code of Iran |
E706410
|
entity |
| Predicate | definesCrimeType |
P26615
|
FINISHED |
| Object | apostasy (in some interpretations and practice) |
—
|
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: apostasy (in some interpretations and practice) | Statement: [Islamic Penal Code of Iran, definesCrimeType, apostasy (in some interpretations and practice)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesCrimeType Context triple: [Islamic Penal Code of Iran, definesCrimeType, apostasy (in some interpretations and practice)]
-
A.
crimeType
Indicates the specific category or nature of the crime associated with an event or entity.
-
B.
criminalType
Indicates the specific category or classification of crime associated with a criminal act or offender.
-
C.
committedCrime
Indicates that an entity has carried out or been responsible for a criminal act or offense.
-
D.
crimeCharged
Indicates that legal authorities have formally accused an entity of committing a specific crime.
-
E.
definesOffence
chosen
Indicates that one entity specifies or establishes the nature, elements, or scope of an offence associated with 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 27, 2026, 7:39 p.m.