Triple
T38463163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Overwatch League season |
E912499
|
entity |
| Predicate | playoffsCity |
P146817
|
FINISHED |
| Object | New York City |
—
|
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 City | Statement: [2018 Overwatch League season, playoffsCity, New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffsCity Context triple: [2018 Overwatch League season, playoffsCity, New York City]
-
A.
playoffsDetermine
Indicates that the outcome of playoff competitions decides or establishes a particular result, status, or ranking between the involved entities.
-
B.
playoffVenue
chosen
Indicates the location or facility where a playoff game or playoff series is held.
-
C.
playoffConference
Indicates that a team participates in the playoffs within a specific conference (e.g., Eastern or Western) of a sports league.
-
D.
game6City
Indicates that a game or sporting event took place in, or is associated with, a particular city.
-
E.
playoffContext
Indicates that the relationship or action occurs within the setting or circumstances of a playoff or postseason competition.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:31 p.m.