Triple
T55089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beavers |
E1086
|
entity |
| Predicate | baseballProgramStatus |
P2579
|
FINISHED |
| Object | nationally prominent |
—
|
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: nationally prominent | Statement: [Beavers, baseballProgramStatus, nationally prominent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseballProgramStatus Context triple: [Beavers, baseballProgramStatus, nationally prominent]
-
A.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
-
B.
leaguePennants
Indicates that a team has won a specified number of league pennants (championship titles) in a particular league.
-
C.
ballpark
Indicates an approximate or rough estimation of a value, rather than an exact or precise figure.
-
D.
finalMLBTeam
Indicates the Major League Baseball team with which an entity was last or ultimately associated, such as the final team they played for or were on the roster of.
-
E.
hasPrimeTimeGames
Indicates that an entity (such as a team, league, or event) is associated with games scheduled during prime-time viewing hours.
- F. None of above. chosen
Provenance (4 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b3a9e848190b80de3c858678b3a |
completed | Feb. 28, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69a24ac52fb08190aa7c38f83434f795 |
completed | Feb. 28, 2026, 1:54 a.m. |
| PDg | Predicate description generation | batch_69a24b39eef081909cec4333f2b25513 |
completed | Feb. 28, 2026, 1:56 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.