Triple
T2454485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hallway Series |
E53786
|
entity |
| Predicate | rivalryFeature |
P39968
|
FINISHED |
| Object | teams share same home arena |
—
|
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: teams share same home arena | Statement: [Hallway Series, rivalryFeature, teams share same home arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryFeature Context triple: [Hallway Series, rivalryFeature, teams share same home arena]
-
A.
rivalryCharacterization
Indicates a relationship in which two entities are characterized as rivals, typically defined by ongoing competition, opposition, or conflict between them.
-
B.
typeOfRivalry
Indicates a competitive or adversarial relationship between entities, specifying the particular kind or nature of rivalry that exists between them.
-
C.
rivalOf
Indicates a relationship in which two entities compete against or oppose each other, often seeking advantage in the same domain or objective.
-
D.
rivalryName
Indicates that a specific name or label is assigned to a rivalry relationship between two entities.
-
E.
rivalryLevel
Indicates the degree or intensity of competitive opposition or conflict between two entities.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0aed2688190a18fe66b98d80e0b |
completed | March 7, 2026, 7:15 a.m. |
| PDg | Predicate description generation | batch_69abd2baee308190bdaa41ef1f6bc9cc |
completed | March 7, 2026, 7:24 a.m. |
Created at: March 6, 2026, 9:44 p.m.