Triple
T20255768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amelia Vanek |
E498696
|
entity |
| Predicate | attemptsAction |
P58482
|
FINISHED |
| Object | destroy The Babadook book |
—
|
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: destroy The Babadook book | Statement: [Amelia Vanek, attemptsAction, destroy The Babadook book]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptsAction Context triple: [Amelia Vanek, attemptsAction, destroy The Babadook book]
-
A.
attemptedAction
chosen
Indicates that an entity made an effort to perform a particular action, regardless of whether the action was successfully completed.
-
B.
attemptNumber
Indicates the specific ordinal count of attempts made for a given action or process.
-
C.
launchAttemptNumber
Indicates the ordinal count of attempts made to launch something, typically specifying which numbered try a particular launch event represents.
-
D.
attemptLimit
Indicates a restriction on how many times an action or operation may be attempted before it is stopped or blocked.
-
E.
wasTriedAt
Indicates that a legal case or judicial proceeding involving an entity took place at a specific court or location.
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673ab60388190be32cc69bf2b6f76 |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:41 p.m.