Triple
T19760538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bearcat Stadium |
E474616
|
entity |
| Predicate | hasHomeTeamAchievement |
P33065
|
FINISHED |
| Object | multiple NCAA Division II national championships |
—
|
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: multiple NCAA Division II national championships | Statement: [Bearcat Stadium, hasHomeTeamAchievement, multiple NCAA Division II national championships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeTeamAchievement Context triple: [Bearcat Stadium, hasHomeTeamAchievement, multiple NCAA Division II national championships]
-
A.
hasHomeTeamLevel
Indicates that an entity is associated with the competitive level or tier of the home team involved in a game or event.
-
B.
hasHomeTeamType
Indicates that an entity has a specified classification or category for its home team (e.g., type or role of the home team in a competition).
-
C.
goalsHomeTeam
Indicates the number of goals scored by the home team in a match.
-
D.
hostedTeamAchievement
chosen
Indicates that an entity organized or hosted an event or context in which a team achieved a particular accomplishment.
-
E.
homeTeamChampion
Indicates that the team playing at home is the champion or title-holding team in the given 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6531f38b48190b1663870a8da5a59 |
completed | April 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.