Triple
T8846264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Ural Yekaterinburg |
E210511
|
entity |
| Predicate | hasHomeStadiumType |
P21483
|
FINISHED |
| Object | multi-purpose stadium |
—
|
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: multi-purpose stadium | Statement: [FC Ural Yekaterinburg, hasHomeStadiumType, multi-purpose stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeStadiumType Context triple: [FC Ural Yekaterinburg, hasHomeStadiumType, multi-purpose stadium]
-
A.
homeStadiumType
chosen
Indicates the type or classification of a venue that serves as a team's primary home stadium.
-
B.
hostStadiumType
Indicates the type or category of stadium that serves as the host venue for an event or activity.
-
C.
hasTeamStadium
Indicates that a sports team is associated with or plays its home games at a particular stadium.
-
D.
hasHostStadiumTeam
Indicates that a particular team is the primary host or home team for events held at a given stadium.
-
E.
homeStadiumOf
Indicates that a particular stadium serves as the primary home venue for a specific sports team or organization.
- 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_69ca838967bc8190b46c3c80a2887ea4 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60a7c518819095399976148e1b9a |
completed | April 1, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:48 p.m.