Triple
T11546405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moneybags |
E273784
|
entity |
| Predicate | targetOfPlayerReaction |
P100035
|
FINISHED |
| Object | often disliked by players for his greed |
—
|
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: often disliked by players for his greed | Statement: [Moneybags, targetOfPlayerReaction, often disliked by players for his greed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetOfPlayerReaction Context triple: [Moneybags, targetOfPlayerReaction, often disliked by players for his greed]
-
A.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
B.
aimedAtBy
Indicates that one entity serves as the target or goal toward which another entity directs an action, intention, or focus.
-
C.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
D.
targetOfIntervention
Indicates that an entity is the object or focus upon which an intervention, treatment, or action is directed.
-
E.
symbolicRoleOfTarget
Indicates that the target entity serves as a symbolic representation or emblem for another entity or concept.
- F. None of above. chosen
Provenance (4 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e3ad548190b2c88332f5d919bd |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822f00a088190ac6b48e45e743899 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:37 p.m.