Triple
T27976091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derby-ye Tehrān |
E706493
|
entity |
| Predicate | homeStadiumOfMostMatches |
P2439
|
FINISHED |
| Object | Azadi Stadium, Tehran |
—
|
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: Azadi Stadium, Tehran | Statement: [Derby-ye Tehrān, homeStadiumOfMostMatches, Azadi Stadium, Tehran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStadiumOfMostMatches Context triple: [Derby-ye Tehrān, homeStadiumOfMostMatches, Azadi Stadium, Tehran]
-
A.
mainStadium
chosen
Indicates that a particular stadium serves as the primary or home stadium associated with an entity (such as a team, club, or organization).
-
B.
isLargestStadiumIn
Indicates that a stadium is the largest (by capacity or size) among all stadiums located within a specified geographic or administrative area.
-
C.
mainCityStadium
Indicates that a stadium serves as the primary or main stadium for a given city.
-
D.
countryNationalStadiumOf
Indicates that a given stadium serves as the official national stadium of a specified country.
-
E.
WorldCupVenue
Indicates that a location serves or has served as a venue where World Cup matches are held.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 7:41 p.m.