Triple
T9889803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qin law code |
E181423
|
entity |
| Predicate | punishmentsIncluded |
P3012
|
FINISHED |
| Object | corporal punishment |
—
|
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: corporal punishment | Statement: [Qin law code, punishmentsIncluded, corporal punishment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: punishmentsIncluded Context triple: [Qin law code, punishmentsIncluded, corporal punishment]
-
A.
hasPunishment
chosen
Indicates that an entity is subject to a specified penalty, sanction, or adverse consequence as a result of some action, condition, or rule.
-
B.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
C.
punishmentOfPeople
Indicates that a person or group is subjected to a punitive action or sanction by another entity or authority.
-
D.
punishmentDescribedAs
Indicates that one entity characterizes, labels, or portrays a punishment using a particular description or term.
-
E.
aimOfPunishment
Indicates that a specified purpose or objective is the intended goal or rationale behind a particular act of punishment.
- 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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb47dfa908190884e96e5e5d6f41f |
completed | April 2, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:39 p.m.