Triple
T5866445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gonzaga Bulldogs men's basketball |
E130405
|
entity |
| Predicate | hasAchieved |
P1518
|
FINISHED |
| Object | multiple NCAA Tournament appearances |
—
|
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 Tournament appearances | Statement: [Gonzaga Bulldogs men's basketball, hasAchieved, multiple NCAA Tournament appearances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAchieved Context triple: [Gonzaga Bulldogs men's basketball, hasAchieved, multiple NCAA Tournament appearances]
-
A.
achieved
chosen
Indicates that an entity successfully reached, obtained, or accomplished a specified goal, result, or state.
-
B.
achievementStatus
Indicates the current state or level of completion of an achievement-related goal or milestone for an entity.
-
C.
hasHad
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
-
D.
canAchieve
Indicates that an entity has the ability or potential to successfully attain or accomplish a specified goal, state, or outcome.
-
E.
hasAwarded
Indicates that one entity has given or conferred an award to another entity.
- 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_69c0085047dc8190af24e311edad3c07 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ffaef081909faaa7f420a3b9b7 |
completed | March 22, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69c03347e51c81909053bcf34e3b88ab |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:56 p.m.