Triple
T22727887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Boroughs |
E562045
|
entity |
| Predicate | featuresPreseasonGames |
P61479
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Battle of the Boroughs, featuresPreseasonGames, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPreseasonGames Context triple: [Battle of the Boroughs, featuresPreseasonGames, true]
-
A.
playedPreseasonGames
chosen
Indicates that an entity participated in preseason games, typically before the official competitive season begins.
-
B.
preseasonExpectation
Indicates the anticipated outcome, performance level, or status assigned to an entity before the official season or main event begins.
-
C.
preseasonHomeArena
Indicates the arena where a team plays its home games during the preseason.
-
D.
featuresRegularSeasonGames
Indicates that the subject includes or hosts games that are part of a standard, scheduled regular season competition.
-
E.
featuresRegularSeasonMeetingsPerYear
Indicates that the relationship involves how many regular-season meetings or matchups occur between the entities each year.
- 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1792b22cc819099aa00bb2dbacce3 |
completed | April 29, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:21 p.m.