Triple
T7786809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lokomotiv Moscow |
E187265
|
entity |
| Predicate | cityRivalryContext |
P46046
|
FINISHED |
| Object | Moscow clubs rivalry |
—
|
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: Moscow clubs rivalry | Statement: [Lokomotiv Moscow, cityRivalryContext, Moscow clubs rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityRivalryContext Context triple: [Lokomotiv Moscow, cityRivalryContext, Moscow clubs rivalry]
-
A.
cityRivalry
Indicates a competitive or adversarial relationship that exists between two cities, often involving sports, economics, culture, or historical tensions.
-
B.
rivalryInvolvesCity
chosen
Indicates that a rivalry relationship includes or is associated with a particular city as one of its involved locations.
-
C.
countryRivalryContext
Indicates a relationship where two countries are in a state of rivalry, competition, or conflict within a specific political, historical, or strategic context.
-
D.
hasLocalRivalry
Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
-
E.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
- 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_69ca82af2d2c8190963861f5e0b8bf21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
Created at: March 30, 2026, 4:24 p.m.