Triple
T493083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1915 National League pennant |
E10230
|
entity |
| Predicate | pennantClinchedYear |
P2961
|
FINISHED |
| Object | 1915 |
—
|
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: 1915 | Statement: [1915 National League pennant, pennantClinchedYear, 1915]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pennantClinchedYear Context triple: [1915 National League pennant, pennantClinchedYear, 1915]
-
A.
wonStanleyCupInYear
Indicates that a team secured victory in the Stanley Cup championship in the specified year.
-
B.
leaguePennant
chosen
Indicates that a team has won the championship pennant for a particular league or season.
-
C.
tripleCrownYear
Indicates the year in which an entity achieved a Triple Crown title or completed a Triple Crown accomplishment.
-
D.
lastSeasonChampion
Indicates that the subject is the champion or winner of the immediately preceding season of the relevant competition or event.
-
E.
pennantTeam
Indicates that a team has won or represents the league or conference pennant for a given season or competition.
- 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.