Triple
T6527813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quinnipiac Bobcats men's ice hockey |
E151349
|
entity |
| Predicate | frozenFourAppearances |
P12672
|
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: [Quinnipiac Bobcats men's ice hockey, frozenFourAppearances, multiple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frozenFourAppearances Context triple: [Quinnipiac Bobcats men's ice hockey, frozenFourAppearances, multiple]
-
A.
frozenFourParticipants
Indicates that the entities are teams that qualified for and participated in the NCAA Division I men’s ice hockey Frozen Four tournament in a given year.
-
B.
finalFourAppearancesWith
Indicates that the entities have appeared together in the NCAA basketball Final Four in the same tournament.
-
C.
finalFourAppearance
chosen
Indicates that an entity has reached the semifinal round (Final Four) of a tournament or championship.
-
D.
portrayedInFranchise
Indicates that an entity is depicted as a character or element within a specific media franchise.
-
E.
frozenIn
Indicates that one entity is immobilized or preserved in a solid, frozen state within or by 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ada9c8408190b1bc327985366be9 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:46 p.m.