Triple
T29518131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beijing Derby |
E748856
|
entity |
| Predicate | hasHomeCityStadium |
P185209
|
FINISHED |
| Object | Workers' Stadium (for Beijing Guoan home derbies) |
—
|
NE NERFINISHED |
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: Workers' Stadium (for Beijing Guoan home derbies) | Statement: [Beijing Derby, hasHomeCityStadium, Workers' Stadium (for Beijing Guoan home derbies)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeCityStadium Context triple: [Beijing Derby, hasHomeCityStadium, Workers' Stadium (for Beijing Guoan home derbies)]
-
A.
hasHomeCityTeamStadium
Indicates that a sports team’s home city is associated with a specific stadium where the team primarily hosts its home games.
-
B.
cityOfHomeStadium
Indicates the city in which a given home stadium is located.
-
C.
hasHomeStadiumContext
Indicates that an entity’s home stadium is specified or characterized within a particular contextual framework (such as time, competition, or role).
-
D.
hasHomeCity
Indicates that an entity’s primary or official city of residence or affiliation is a specified city.
-
E.
homeCityForMajorStadium
Indicates that a city serves as the home location for a particular major stadium.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bbf812cc8190a16917c5daaff2df |
completed | May 3, 2026, 9:19 p.m. |
Created at: April 28, 2026, 4:38 p.m.