Triple
T19819363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Joe |
E476144
|
entity |
| Predicate | servedAsHomeArenaEndYear |
P904
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [The Joe, servedAsHomeArenaEndYear, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsHomeArenaEndYear Context triple: [The Joe, servedAsHomeArenaEndYear, 2017]
-
A.
usedAsHomeArenaFrom
Indicates that a particular venue served as the home arena for an entity (such as a team) starting from a specified point in time.
-
B.
formerHomeArena
chosen
Indicates that a venue previously served as the primary home arena for a team or organization but no longer holds that status.
-
C.
replacedAsPrimaryBasketballVenueBy
Indicates that one basketball venue ceased to be the main or primary location for games or events and was succeeded in that role by another venue.
-
D.
cityOfChampionHomeArena
Indicates that a city is the home location of the arena where a champion’s team or individual competitor plays or competes.
-
E.
franchiseEndYear
Indicates the calendar year in which a franchise relationship or agreement is terminated or ceases to operate.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654fc8b94819095fd5240f33b6713 |
completed | April 20, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.