Triple
T470197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle SuperSonics |
E8537
|
entity |
| Predicate | numberOfDivisionTitles |
P549
|
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: [Seattle SuperSonics, numberOfDivisionTitles, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfDivisionTitles Context triple: [Seattle SuperSonics, numberOfDivisionTitles, 6]
-
A.
divisionTitles
chosen
Indicates that an entity holds or is associated with one or more titles or championships within a specific division or category.
-
B.
wonDivisionTitle
Indicates that an entity secured first place in its competitive division, earning the division championship title.
-
C.
hasChampionships
Indicates that one entity possesses or has won one or more championships associated with another entity.
-
D.
mastersTitles
Indicates that one entity holds one or more master's degree titles associated with another entity (such as an institution, field, or program).
-
E.
wonLeagueTitle
Indicates that a team or individual finished a competition as champions, securing the league title for that season or tournament.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efef8b788190857ebf66df562d59 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edebb3988190907992a584b4e260 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.