Triple
T493127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1983 National League pennant |
E10231
|
entity |
| Predicate | PhilliesRegularSeasonRecord |
P10319
|
FINISHED |
| Object | 90–72 |
—
|
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: 90–72 | Statement: [1983 National League pennant, PhilliesRegularSeasonRecord, 90–72]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PhilliesRegularSeasonRecord Context triple: [1983 National League pennant, PhilliesRegularSeasonRecord, 90–72]
-
A.
NLTeamRegularSeasonRecord
chosen
Indicates the win–loss (and often tie) performance record of a National League baseball team over a regular season.
-
B.
ALTeamRegularSeasonRecord
Indicates the relationship that specifies a team's win–loss record during the American League regular season.
-
C.
championRegularSeasonRecord
Indicates that an entity is the champion associated with a particular regular season record.
-
D.
bestSeasonRecord
Indicates that one entity holds the best (most successful) season performance record among a set of entities, typically in a competitive or statistical context.
-
E.
gameCountWonByPittsburghPirates
Indicates the number of games that were won by the Pittsburgh Pirates.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f0faab4881909f65f172198b5bd2 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edf7ce008190836fb6ab5ea39375 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.