Triple
T13474311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA softball |
E318210
|
entity |
| Predicate | usesEquipmentStandard |
P1587
|
FINISHED |
| Object | NCAA-approved bats |
—
|
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: NCAA-approved bats | Statement: [NCAA softball, usesEquipmentStandard, NCAA-approved bats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEquipmentStandard Context triple: [NCAA softball, usesEquipmentStandard, NCAA-approved bats]
-
A.
usesEquipment
Indicates that an entity employs or operates a particular piece of equipment to perform an action or fulfill a function.
-
B.
usesStandard
chosen
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
C.
typeOfEquipmentUsed
Indicates that a particular piece or category of equipment is utilized in performing a specific action, process, or activity.
-
D.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
E.
standardEquipmentOrigin
Indicates that an item’s standard equipment comes from or is originally supplied by a specified source or origin.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf2447bc81908baf1f4b55095144 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.