Triple
T35387060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buster Beetle |
E1022817
|
entity |
| Predicate | throwsAt |
P2172
|
FINISHED |
| Object | Mario |
—
|
NE NERFINISHED |
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: Mario | Statement: [Buster Beetle, throwsAt, Mario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: throwsAt Context triple: [Buster Beetle, throwsAt, Mario]
-
A.
throws
chosen
Indicates that one entity propels or hurls another entity or object through space, typically by a deliberate physical action.
-
B.
throwsException
Indicates that an operation or method results in an exception being raised during its execution.
-
C.
throwsUpTo
Indicates that an entity propels or sends something in an upward direction toward a specified target or limit.
-
D.
thrownAtRuntime
Indicates that an exception or error condition is raised during the execution of a program rather than at compile time.
-
E.
thrownThrough
Indicates that one entity has been propelled with force so that it passes through another entity or barrier.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f794f649648190a79d90e6e67fe2dc |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.