Triple
T27462926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Cosmos |
E692798
|
entity |
| Predicate | rebootEraCompetition |
P163265
|
FINISHED |
| Object | U.S. Open Cup |
—
|
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: U.S. Open Cup | Statement: [New York Cosmos, rebootEraCompetition, U.S. Open Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebootEraCompetition Context triple: [New York Cosmos, rebootEraCompetition, U.S. Open Cup]
-
A.
rebootEraHomeStadium
Indicates that a particular stadium serves as the home venue for a team or entity during a specific reboot era.
-
B.
competitionEra
Indicates the historical or contextual period during which a particular competition or competitive event took place.
-
C.
rebootSeason
Indicates that a media series has been restarted or reimagined in a new season, typically resetting or significantly altering its prior continuity.
-
D.
recompetitionYear
Indicates the year in which a previously awarded or existing arrangement is opened again for competitive selection or bidding.
-
E.
replacementCompetition
Indicates a relationship where one entity competes to take over or replace the role, position, or function currently held by another entity.
- F. None of above. chosen
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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6369a22688190a5674191c90a5d12 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 12:50 p.m.