Triple
T1198949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA play-in tournament |
E25733
|
entity |
| Predicate | eligibleSeedsPerConference |
P25483
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [NBA play-in tournament, eligibleSeedsPerConference, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleSeedsPerConference Context triple: [NBA play-in tournament, eligibleSeedsPerConference, 7]
-
A.
playoffSeed
Indicates the ranking or position a team or player holds in a playoff bracket based on their performance or qualification criteria.
-
B.
numberOfDivisionsInConference
Indicates the total count of divisions that exist within a given conference.
-
C.
teamsPerConference
Indicates the number of teams that are associated with or belong to a given conference.
-
D.
hasPlayoffSeedingBasis
Indicates that an entity’s playoff seeding is determined or justified based on a specified rule, criterion, or basis.
-
E.
hasAutomaticPlayoffBids
Indicates that certain participants are guaranteed entry into a playoff competition without needing to qualify through regular selection or performance criteria.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9d56748190a12fe4a30346f1d8 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5ed2b88190aab992913957e1cf |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bcc82e38819081c3615e1cc7a66f |
completed | March 1, 2026, 10:25 p.m. |
Created at: March 1, 2026, 7:46 p.m.