Triple
T7317750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salih |
E168456
|
entity |
| Predicate | peoplePunishedFor |
P73633
|
FINISHED |
| Object | killing the she-camel |
—
|
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: killing the she-camel | Statement: [Salih, peoplePunishedFor, killing the she-camel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peoplePunishedFor Context triple: [Salih, peoplePunishedFor, killing the she-camel]
-
A.
punishmentOfPeople
chosen
Indicates that a person or group is subjected to a punitive action or sanction by another entity or authority.
-
B.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
C.
convictedIndividual
Indicates that an individual has been found guilty of a crime or offense through a formal legal process and has received a conviction.
-
D.
aimOfPunishment
Indicates that a specified purpose or objective is the intended goal or rationale behind a particular act of punishment.
-
E.
timeOfCondemnation
Indicates the specific time at which a condemnation (such as a legal judgment or formal denunciation) occurs or is issued.
- 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_69c68a5251508190ad68df4151cfeb04 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ef178b3081908cd0c62466069741 |
completed | March 27, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:02 p.m.