Triple
T6002455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1988 NCAA men's basketball championship |
E133628
|
entity |
| Predicate | seedOfWinner |
P68605
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [1988 NCAA men's basketball championship, seedOfWinner, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seedOfWinner Context triple: [1988 NCAA men's basketball championship, seedOfWinner, 6]
-
A.
runnerUpSeed
Indicates that one entity is the competitor or team assigned the second-best (runner-up) seed or ranking in a tournament or competition relative to another entity.
-
B.
winnerGeneration
Indicates that an entity is responsible for producing, determining, or designating the winner in a given context or competition.
-
C.
championSeed
Indicates that an entity is designated as the top or primary seed (expected winner) in a competitive event or tournament.
-
D.
winnerManager
Indicates that one entity is the manager or supervisor of another entity who is the winner in a given context or competition.
-
E.
firstWinner
Indicates that the subject is the entity who achieved first place or victory in the referenced event or competition.
- 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_69c04ee9cb0c8190a3361c36ac3944af |
completed | March 22, 2026, 8:19 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:05 p.m.