Triple
T9760344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1984 National League Championship Series |
E236652
|
entity |
| Predicate | team1LeagueTitle |
P90858
|
FINISHED |
| Object | National League East champion |
—
|
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: National League East champion | Statement: [1984 National League Championship Series, team1LeagueTitle, National League East champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: team1LeagueTitle Context triple: [1984 National League Championship Series, team1LeagueTitle, National League East champion]
-
A.
team1League
Indicates the league or competition in which the first team (team1) participates or is classified.
-
B.
team1LeagueTitles
Indicates the number of league titles that the first team has won.
-
C.
leagueName
Indicates the official name assigned to a particular sports league or competitive organization.
-
D.
team2LeagueTitlesContext
Indicates that the second team has won league titles within a specified contextual scope (such as a particular time period, competition, or condition).
-
E.
team2LeagueTitles
Indicates that a given team has won a specified number of league titles.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda049995c81908569ec61805642b2 |
completed | April 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd081a9c5c819093439be7e802ff85 |
completed | April 1, 2026, 11:57 a.m. |
Created at: March 30, 2026, 8:25 p.m.