Triple
T1343568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lokomotiv Yaroslavl |
E28518
|
entity |
| Predicate | homeGames |
P20883
|
FINISHED |
| Object | played at Arena 2000 in Yaroslavl |
—
|
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: played at Arena 2000 in Yaroslavl | Statement: [Lokomotiv Yaroslavl, homeGames, played at Arena 2000 in Yaroslavl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeGames Context triple: [Lokomotiv Yaroslavl, homeGames, played at Arena 2000 in Yaroslavl]
-
A.
homeGamesCountry
Indicates the country in which an entity’s home games are played.
-
B.
videoGame
Indicates that one entity is a video game associated with, created by, or otherwise related to another entity.
-
C.
seriesGame
Indicates that a game is part of, or belongs to, a particular series or franchise.
-
D.
hasGamesAt
chosen
Indicates that a particular location, venue, or platform hosts or offers one or more games.
-
E.
notableGame
Indicates that a particular game is especially significant, prominent, or well-known in relation to the associated entity.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c23b8a9081908b78405d4ef806af |
completed | March 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69a4bef3e8fc8190ac9a1ba9b5879483 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.