Triple
T22745723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crosstown Shootout |
E562547
|
entity |
| Predicate | hasRivalryTrophies |
P82076
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Crosstown Shootout, hasRivalryTrophies, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRivalryTrophies Context triple: [Crosstown Shootout, hasRivalryTrophies, false]
-
A.
hasRivalryTrophyStatus
chosen
Indicates that a rivalry trophy has a particular status or condition within the context of a competitive relationship.
-
B.
isRivalryTrophyFor
Indicates that an object serves as the trophy awarded in a rivalry competition between specific entities.
-
C.
hasRivalryCategory
Indicates that there exists a competitive or adversarial relationship between entities that falls into a specific classified type or category of rivalry.
-
D.
hasRivalryAspect
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
-
E.
trophyContestedBy
Indicates that a particular trophy is the object of competition among the specified participants or teams.
- 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_69e245513a5c81908d5cb471b4fc429d |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179b563e481908804d07fca1777b9 |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:23 p.m.