Triple
T6003070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notre Dame Fighting Irish men's basketball |
E133641
|
entity |
| Predicate | EliteEightAppearances |
P68623
|
FINISHED |
| Object | multiple |
—
|
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 | Statement: [Notre Dame Fighting Irish men's basketball, EliteEightAppearances, multiple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EliteEightAppearances Context triple: [Notre Dame Fighting Irish men's basketball, EliteEightAppearances, multiple]
-
A.
runnerUpConsecutiveAppearances
Indicates that an entity has achieved runner-up status in a competition for a specified number of consecutive appearances or editions.
-
B.
isStarterPokémonIn
Indicates that a Pokémon serves as a starter Pokémon within a specified game, region, or context.
-
C.
allStarAppearances
Indicates the number of times an entity has been selected to participate in an All-Star event or game.
-
D.
WorldChampionshipAppearances
Indicates the number of times an entity has participated in a world championship competition.
-
E.
worldSeriesAppearance
Indicates that an entity (typically a team) has participated in a World Series event.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f0f63148190826198281dce3713 |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e3316c819087ea635fa7ee8472 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8c5bfc8190b986a7071d1b23e3 |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:06 p.m.