Triple
T33828639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pete Wingfield |
E867030
|
entity |
| Predicate | hadHitSingle |
P142862
|
FINISHED |
| Object | Eighteen with a Bullet |
—
|
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: Eighteen with a Bullet | Statement: [Pete Wingfield, hadHitSingle, Eighteen with a Bullet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadHitSingle Context triple: [Pete Wingfield, hadHitSingle, Eighteen with a Bullet]
-
A.
hitSingle
Indicates that a batter successfully hits the ball and reaches first base safely, recording a single.
-
B.
wasAHitIn
Indicates that something (such as a work, product, or performance) achieved notable success or popularity within a specified context, time period, or location.
-
C.
hitOver
Indicates that one entity strikes or impacts another entity by moving over or across it.
-
D.
isBsideToHitSingle
Indicates that one song serves as the B-side track accompanying another song that is a hit single.
-
E.
hasNotableHit
chosen
Indicates that an entity is associated with a particularly successful, famous, or widely recognized work, performance, or achievement.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7001e32208190978b7195d0b5042e |
completed | May 3, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.