Triple
T15224232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Bartman |
E363834
|
entity |
| Predicate | headphonesUse |
P2728
|
FINISHED |
| Object | listening to radio broadcast during game |
—
|
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: listening to radio broadcast during game | Statement: [Steve Bartman, headphonesUse, listening to radio broadcast during game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headphonesUse Context triple: [Steve Bartman, headphonesUse, listening to radio broadcast during game]
-
A.
hasAcousticUse
Indicates that something is used or functions in relation to sound or acoustics.
-
B.
supports3_5mmJack
Indicates that one entity is compatible with or provides a 3.5mm audio jack connection for another entity.
-
C.
hasMicrophones
Indicates that one entity possesses, includes, or is equipped with one or more microphones.
-
D.
usesEquipment
chosen
Indicates that an entity employs or operates a particular piece of equipment to perform an action or fulfill a function.
-
E.
hasAcousticsSuitableFor
Indicates that something possesses acoustic properties that are appropriate or well-suited for a particular use, activity, or environment.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0078a9318819081db3b7bcc28e04f |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.