Triple
T12855907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittsburgh Steelers–Philadelphia Eagles rivalry |
E307453
|
entity |
| Predicate | firstSeasonOfPlay |
P106063
|
FINISHED |
| Object | 1933 |
—
|
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: 1933 | Statement: [Pittsburgh Steelers–Philadelphia Eagles rivalry, firstSeasonOfPlay, 1933]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSeasonOfPlay Context triple: [Pittsburgh Steelers–Philadelphia Eagles rivalry, firstSeasonOfPlay, 1933]
-
A.
firstYearPlayed
Indicates the year in which an entity (such as a person or team) first began participating in the specified activity or domain.
-
B.
firstPlayed
Indicates that one entity was the earliest or initial thing (such as a song, game, or media item) that another entity engaged with or played.
-
C.
firstPerformanceSeason
chosen
Indicates the season in which an entity (such as a work or performer) had its first performance.
-
D.
firstSeasonEligible
Indicates that this is the earliest season in which an entity becomes eligible to participate in or receive something.
-
E.
firstSeasonOf
Indicates that one entity is the first season installment belonging to the series or show represented by the other entity.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:37 p.m.