Triple
T13101365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1991 Patrick Division Finals |
E310725
|
entity |
| Predicate | chronologicalOrderInPlayoffs |
P25199
|
FINISHED |
| Object | second round |
—
|
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: second round | Statement: [1991 Patrick Division Finals, chronologicalOrderInPlayoffs, second round]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalOrderInPlayoffs Context triple: [1991 Patrick Division Finals, chronologicalOrderInPlayoffs, second round]
-
A.
playoffHistory
Indicates a relationship detailing an entity’s record, participation, or performance across one or more playoff competitions or seasons.
-
B.
playoffRecord
Indicates the win-loss performance of an entity (such as a team or player) in postseason or playoff competitions.
-
C.
playoffsStartDate
Indicates the calendar date on which a competition’s playoff phase begins.
-
D.
playoffPath
chosen
Indicates the sequence of games, rounds, or matchups a team or player must progress through in a playoff tournament.
-
E.
playoffMeetingsEra
Indicates that two entities have faced each other in playoff competition during a specified historical era or time period.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981515d488190908d3cca1b84a42d |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:04 p.m.