Triple
T17885238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardware |
E447182
|
entity |
| Predicate | protagonistFights |
P101399
|
FINISHED |
| Object | corruption |
—
|
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: corruption | Statement: [Hardware, protagonistFights, corruption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistFights Context triple: [Hardware, protagonistFights, corruption]
-
A.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
B.
diesFighting
Indicates that an entity dies as a direct result of engaging in a fight or combat.
-
C.
protagonistAction
chosen
Indicates that the referenced entity performs the central or primary action associated with the main character in a narrative or scenario.
-
D.
hasFightSceneWith
Indicates that two entities participate together in a fight scene or combat sequence.
-
E.
hasAntagonisticProtagonist
Indicates that the work features a main character who opposes or undermines the typical heroic or moral expectations of a traditional protagonist.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49c123748819091bf46178105079b |
completed | April 19, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:18 a.m.