Triple
T23625451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katiyana Mauga |
E583449
|
entity |
| Predicate | homeRunsCharacteristic |
P62835
|
FINISHED |
| Object | prolific home run hitter |
—
|
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: prolific home run hitter | Statement: [Katiyana Mauga, homeRunsCharacteristic, prolific home run hitter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeRunsCharacteristic Context triple: [Katiyana Mauga, homeRunsCharacteristic, prolific home run hitter]
-
A.
homeRuns
Indicates the number of home runs a player hits, or that a specific home run event occurs, in a baseball context.
-
B.
homeRunType
Indicates the specific kind of home run that was hit in a baseball play (e.g., solo, two-run, three-run, grand slam).
-
C.
homeRunRate
Indicates the frequency at which a player or team hits home runs relative to a specified number of opportunities (such as at-bats, plate appearances, or games).
-
D.
homeRunHittingAbility
Indicates the capability or skill level of an entity to hit home runs.
-
E.
homeRunsNotedFor
chosen
Indicates that an entity is recognized or recorded specifically for its home runs.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b17c993c8190bf9ee3201869d240 |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.