Triple
T2648835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miami Dolphins–New York Jets rivalry |
E53847
|
entity |
| Predicate | team2Founded |
P5807
|
FINISHED |
| Object | 1960 |
—
|
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: 1960 | Statement: [Miami Dolphins–New York Jets rivalry, team2Founded, 1960]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: team2Founded Context triple: [Miami Dolphins–New York Jets rivalry, team2Founded, 1960]
-
A.
team2Established
chosen
Indicates that a second team (team2) has been formally created or founded at a specific point in time.
-
B.
team1Established
Indicates that the first team in a given context has been founded or formally established.
-
C.
teamFoundedLegacy
Indicates that a team was established as a continuation, successor, or legacy of a prior organization or team.
-
D.
team1FoundedAsCurrentName
Indicates that the first team entity was originally founded under its current name, rather than having changed names since its founding.
-
E.
associatedClubFounded
Indicates that there exists a club associated with an entity and specifies the date or time at which that associated club was founded.
- 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.