Triple
T3937694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boise State Broncos |
E90953
|
entity |
| Predicate | footballAchievement |
P17391
|
FINISHED |
| Object | multiple conference 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 conference championships | Statement: [Boise State Broncos, footballAchievement, multiple conference championships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footballAchievement Context triple: [Boise State Broncos, footballAchievement, multiple conference championships]
-
A.
FIFABallonDorWinner
Indicates that the subject is the football player who won the FIFA Ballon d'Or award in the specified year or context.
-
B.
sportsAchievement
chosen
Indicates a relationship where an entity attains or is recognized for a notable accomplishment in a sports context.
-
C.
fifaWorldPlayerOfTheYear
Indicates that one entity has been awarded the FIFA World Player of the Year title for a given year or period.
-
D.
playerOfTheMatch
Indicates that the subject was recognized as the standout performer (best player) in a particular match.
-
E.
goalScorer
Indicates that the subject is the player who scored a particular goal in a game or match.
- 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedcfd7d48190bbacee8b5b1b5070 |
completed | March 9, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.