Triple
T38020477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wellington Wells |
E948614
|
entity |
| Predicate | punishmentForNonCompliance |
P82264
|
FINISHED |
| Object | being labeled a Downer |
—
|
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: being labeled a Downer | Statement: [Wellington Wells, punishmentForNonCompliance, being labeled a Downer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: punishmentForNonCompliance Context triple: [Wellington Wells, punishmentForNonCompliance, being labeled a Downer]
-
A.
punishmentIncludes
Indicates that a specified punishment encompasses or contains another specified punitive measure as one of its components.
-
B.
providesForPunishment
Indicates that one entity establishes or authorizes a penalty or sanction to be imposed on another entity or for a particular action.
-
C.
legalStatusOfNoncompliance
chosen
Indicates the legal characterization or consequences assigned to an instance of noncompliance with a rule, law, or obligation.
-
D.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
E.
reasonForPunishment
Indicates that one entity is the cause, justification, or grounds for another entity receiving a 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.