Triple
T34686998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Generals |
E890779
|
entity |
| Predicate | hasAlternateTeamNames |
P183468
|
FINISHED |
| Object | New York Nationals |
—
|
NE NERFINISHED |
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: New York Nationals | Statement: [Washington Generals, hasAlternateTeamNames, New York Nationals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternateTeamNames Context triple: [Washington Generals, hasAlternateTeamNames, New York Nationals]
-
A.
previousTeamNamesAlsoAssociatedWithFranchise
Indicates that the earlier team names are also historically or officially linked to the same franchise.
-
B.
team1LaterKnownAs
Indicates that the first team was later renamed to or became known by the identity of the second team.
-
C.
teamNameVariant
chosen
Indicates that one team name is an alternative or variant form of another team’s name.
-
D.
team2FormerName
Indicates that the second team entity was previously known by a different name.
-
E.
formerTeam2Name
Indicates that an entity was previously associated with a second former team identified by this name.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: May 1, 2026, 2:05 a.m.