Triple
T28870675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rivalry |
E732131
|
entity |
| Predicate | notableGame150thCity |
P203533
|
FINISHED |
| Object | New York City |
E40
|
NE 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: New York City | Statement: [The Rivalry, notableGame150thCity, New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGame150thCity Context triple: [The Rivalry, notableGame150thCity, New York City]
-
A.
notableGame150thVenue
Indicates that a venue is notable for hosting the 150th instance of a particular game or match.
-
B.
notableGame
Indicates that a particular game is especially significant, prominent, or well-known in relation to the associated entity.
-
C.
cityOfGames
Indicates that a location is recognized as a major center or hub for games, gaming activities, or the games industry.
-
D.
notableGameNumber
chosen
Indicates that a specific game in a series or schedule is distinguished as notable or significant (e.g., by its sequence number).
-
E.
Game1City
Indicates that a game (or sporting event) takes place in, or is associated with, a particular city.
- F. None of above.
Provenance (4 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a01a18e350481909f848686568d19bc |
completed | May 11, 2026, 9:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25058c48c88190b79fa0a056615cc9 |
completed | June 7, 2026, 5:45 a.m. |
| PD | Predicate disambiguation | batch_6a01a121b67c81908a6c5be9eb8e9ca5 |
completed | May 11, 2026, 9:28 a.m. |
Created at: April 28, 2026, 7:32 a.m.