Triple
T17517989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Retribution |
E426613
|
entity |
| Predicate | modifiesSystem |
P104561
|
FINISHED |
| Object | bounty placement rules |
—
|
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: bounty placement rules | Statement: [Retribution, modifiesSystem, bounty placement rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modifiesSystem Context triple: [Retribution, modifiesSystem, bounty placement rules]
-
A.
modificationProgram
chosen
Indicates that an entity is subject to, or associated with, a program or process that alters, updates, or changes its properties or state.
-
B.
packageSystem
Indicates a relationship where an item or component is organized, bundled, or managed within a particular packaging or distribution system.
-
C.
treatsSystem
Indicates that one entity provides medical or remedial care or intervention to a system (such as a bodily system, technical system, or organizational system) to address problems, maintain function, or improve its condition.
-
D.
modifiesFacility
Indicates a relationship where an entity changes, updates, or alters some aspect of a facility (such as its structure, function, or configuration).
-
E.
definesSystemAs
Indicates that one entity explicitly specifies or establishes another entity as the system to be used, referenced, or treated as authoritative.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d0daa48190be69aff32b0324bc |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.