Triple
T28639079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bludger |
E724869
|
entity |
| Predicate | hitWith |
P54554
|
FINISHED |
| Object | Beater’s bat |
—
|
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: Beater’s bat | Statement: [Bludger, hitWith, Beater’s bat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hitWith Context triple: [Bludger, hitWith, Beater’s bat]
-
A.
hitOver
Indicates that one entity strikes or impacts another entity by moving over or across it.
-
B.
hitSingle
Indicates that a batter successfully hits the ball and reaches first base safely, recording a single.
-
C.
wasAHitIn
Indicates that something (such as a work, product, or performance) achieved notable success or popularity within a specified context, time period, or location.
-
D.
hasNotableHit
Indicates that an entity is associated with a particularly successful, famous, or widely recognized work, performance, or achievement.
-
E.
typeOfHit
chosen
Indicates the specific category or kind of hit or strike that occurred in an interaction or event.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:42 a.m.