Triple
T22727883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Boroughs |
E562045
|
entity |
| Predicate | rivalryBecameProminentAfter |
P149482
|
FINISHED |
| Object | Brooklyn Nets relocation to Brooklyn |
—
|
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: Brooklyn Nets relocation to Brooklyn | Statement: [Battle of the Boroughs, rivalryBecameProminentAfter, Brooklyn Nets relocation to Brooklyn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryBecameProminentAfter Context triple: [Battle of the Boroughs, rivalryBecameProminentAfter, Brooklyn Nets relocation to Brooklyn]
-
A.
rivalryStartPeriod
Indicates the time period or point at which a rivalry between entities begins.
-
B.
hadPrimaryRivalry
Indicates that one entity was the main or most significant rival of another entity.
-
C.
rivalryBecameAnnual
Indicates that a previously non-recurring rivalry event or competition started occurring on an annual, regularly scheduled basis.
-
D.
rivalryPeriod
Indicates the time span during which two entities are engaged in an ongoing rivalry or competitive relationship.
-
E.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
- 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_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. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:21 p.m.