Triple
T11819011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocco |
E281075
|
entity |
| Predicate | refusesAction |
P59946
|
FINISHED |
| Object | directly killing Florestan |
—
|
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: directly killing Florestan | Statement: [Rocco, refusesAction, directly killing Florestan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refusesAction Context triple: [Rocco, refusesAction, directly killing Florestan]
-
A.
refusedAction
chosen
Indicates that an entity deliberately declined or did not agree to perform a specific action requested, expected, or proposed by another entity.
-
B.
commandRefused
Indicates that an issued command was not accepted or carried out by the intended recipient.
-
C.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
D.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
E.
refusesFurtherHelpTo
Indicates that one entity declines to provide any additional assistance or support to 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e760988190b50d13bba5ef5b43 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.