Triple
T11876325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blunder Bowl |
E282535
|
entity |
| Predicate | usedBecauseOf |
P21011
|
FINISHED |
| Object | sloppy quality of play |
—
|
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: sloppy quality of play | Statement: [Blunder Bowl, usedBecauseOf, sloppy quality of play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBecauseOf Context triple: [Blunder Bowl, usedBecauseOf, sloppy quality of play]
-
A.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
B.
reasonForUse
chosen
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
C.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
D.
justificationUsedBy
Indicates that a particular justification is employed or relied upon by a given entity (such as a person, system, or decision).
-
E.
usedToExplain
Indicates that one entity serves as an explanation or clarification for another entity.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d39d2934819093b9f7006f45e5cb |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.