Triple
T22365837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Conference playoffs |
E552901
|
entity |
| Predicate | higherSeedAdvantage |
P42750
|
FINISHED |
| Object | home-court advantage |
—
|
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: home-court advantage | Statement: [Eastern Conference playoffs, higherSeedAdvantage, home-court advantage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherSeedAdvantage Context triple: [Eastern Conference playoffs, higherSeedAdvantage, home-court advantage]
-
A.
higherSeed
chosen
Indicates that one competitor or participant has been assigned a better (numerically lower) seed or ranking than another in a tournament or ordered competition.
-
B.
topSeedWins
Indicates that in a competitive matchup, the highest-ranked (top-seeded) participant emerges as the winner.
-
C.
secondSeedPlays
Indicates that the competitor or team seeded second participates in a match or event.
-
D.
seedOfWinner
Indicates that one entity is the seed or ranking position assigned to the entity that wins a competition or match.
-
E.
championSeed
Indicates that an entity is designated as the top or primary seed (expected winner) in a competitive event 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1580074dc819091305ac7017000d3 |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.