Triple
T475129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Articles of War (Continental Army) |
E9043
|
entity |
| Predicate | hasTypeOfSanction |
P3012
|
FINISHED |
| Object | flogging |
—
|
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: flogging | Statement: [Articles of War (Continental Army), hasTypeOfSanction, flogging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfSanction Context triple: [Articles of War (Continental Army), hasTypeOfSanction, flogging]
-
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.
hasTypeOfSecrecy
Indicates that something is associated with a particular kind or level of secrecy.
-
C.
bannedBy
Indicates that an entity is prohibited or disallowed as a result of a decision or action taken by another entity.
-
D.
isWithheldBy
Indicates that something (such as information, resources, or permission) is deliberately not given, released, or made available by a particular entity.
-
E.
isSubjectTo
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f039f3d88190a7c93ecbf1bf5f58 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edeed31881908cf43beed410572d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.