Triple
T2648829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miami Dolphins–New York Jets rivalry |
E53847
|
entity |
| Predicate | hasHomeAndHomeSeriesEachSeason |
P39328
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Miami Dolphins–New York Jets rivalry, hasHomeAndHomeSeriesEachSeason, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeAndHomeSeriesEachSeason Context triple: [Miami Dolphins–New York Jets rivalry, hasHomeAndHomeSeriesEachSeason, true]
-
A.
hasHomeAndAwayFormat
chosen
Indicates that a competition, match, or series is structured with both home and away legs or fixtures between the same opponents.
-
B.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
C.
hasSeasonType
Indicates that something is associated with a particular category or type of season (e.g., summer, winter, rainy).
-
D.
numberOfSeasons
Indicates the total count of seasons associated with a particular entity (such as a series, competition, or event).
-
E.
playsSeasonSeries
Indicates that an entity participates as a competitor or team in a particular season of a series or league.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd91b4b3c81908571e85a1621dfc5 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd814298c8190952f05aed43f6bb8 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.