Triple
T15723465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1982 NBA Finals |
E381162
|
entity |
| Predicate | championSeedInConference |
P44525
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [1982 NBA Finals, championSeedInConference, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championSeedInConference Context triple: [1982 NBA Finals, championSeedInConference, 1]
-
A.
championSeed
chosen
Indicates that an entity is designated as the top or primary seed (expected winner) in a competitive event or tournament.
-
B.
regularSeasonTopSeedConference
Indicates that an entity was the highest-ranked (top-seeded) team in its conference during the regular season.
-
C.
eligibleSeedsPerConference
Indicates the specific tournament seed positions within each conference that qualify as eligible under the defined rules or criteria.
-
D.
playoffSeed
Indicates the ranking or position a team or player holds in a playoff bracket based on their performance or qualification criteria.
-
E.
visitingTeamConferenceSeed
Indicates the ranking or seed assigned to the visiting team within its conference for a given competition or season.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb1fdd4819088f3e243263e5f73 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.