Triple
T31348410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batavia Muckdogs |
E799513
|
entity |
| Predicate | currentCompetitionLevel |
P116444
|
FINISHED |
| Object | collegiate summer baseball |
—
|
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: collegiate summer baseball | Statement: [Batavia Muckdogs, currentCompetitionLevel, collegiate summer baseball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentCompetitionLevel Context triple: [Batavia Muckdogs, currentCompetitionLevel, collegiate summer baseball]
-
A.
commonCompetitionLevel
Indicates that two entities participate in competitions that share the same or comparable level of intensity, skill, or ranking.
-
B.
currentCompetition
Indicates that two or more entities are presently engaged in the same ongoing competition or contest.
-
C.
featuredCompetitionLevel
Indicates that a particular competition level is highlighted or given special prominence relative to other levels.
-
D.
primaryCompetitionLevel
Indicates the main or highest level of competition at which an entity primarily competes or operates.
-
E.
competitionLevelOf
chosen
Indicates the degree or intensity of competitiveness associated with an entity, event, or context.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: April 29, 2026, 9:17 p.m.