Triple
T7819904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | triangle offense |
E181101
|
entity |
| Predicate | usedToWin |
P54773
|
FINISHED |
| Object | multiple NBA championships |
—
|
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 NBA championships | Statement: [triangle offense, usedToWin, multiple NBA championships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToWin Context triple: [triangle offense, usedToWin, multiple NBA championships]
-
A.
winnerPreviouslyWon
Indicates that the winner has won the same or a related contest/event at least once before.
-
B.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
-
C.
competitionWonWith
chosen
Indicates that a competition was won using, involving, or in association with a particular participant, method, tool, or resource.
-
D.
wonAgainst
Indicates that one entity achieved victory over another in a competition, conflict, or contest.
-
E.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, 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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cafa06d28881908d62d4c02b45cedd |
completed | March 30, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:41 p.m.