Triple
T13571332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-Mobile Home Run Derby |
E324167
|
entity |
| Predicate | usesPersonnel |
P50783
|
FINISHED |
| Object | batting practice pitcher |
—
|
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: batting practice pitcher | Statement: [T-Mobile Home Run Derby, usesPersonnel, batting practice pitcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPersonnel Context triple: [T-Mobile Home Run Derby, usesPersonnel, batting practice pitcher]
-
A.
personnel
chosen
Indicates that an entity serves as staff or workforce associated with another entity, such as an organization, project, or facility.
-
B.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
C.
usedByPerson
Indicates that something (such as an object, tool, or resource) is utilized or employed by a person.
-
D.
authorizedPersonnel
Indicates that the referenced entity is officially permitted or empowered to access, use, or perform actions within a specified system, resource, or context.
-
E.
appliesToPerson
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific person.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00f5b8881908617f42d227ed137 |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.