Triple
T24515903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clássico (Porto vs Sporting) |
E606368
|
entity |
| Predicate | homeStadiumOfSportingCP |
P136724
|
FINISHED |
| Object | Estádio José Alvalade |
—
|
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: Estádio José Alvalade | Statement: [Clássico (Porto vs Sporting), homeStadiumOfSportingCP, Estádio José Alvalade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStadiumOfSportingCP Context triple: [Clássico (Porto vs Sporting), homeStadiumOfSportingCP, Estádio José Alvalade]
-
A.
homeStadiumSituatedOn
Indicates that a team's home stadium is physically located on or within the grounds of a specified site or area.
-
B.
locatedAtStadiumOfClub
Indicates that something is situated in the stadium that belongs to or is used by a particular sports club.
-
C.
homeStadiumLocatedIn
chosen
Indicates that the home stadium of a sports team or organization is geographically situated within a specified location or region.
-
D.
hasHomeStadiumOfSwindonTown
Indicates that an entity serves as the home stadium for the Swindon Town football club.
-
E.
hasHomeStadiumOfOxfordUnited
Indicates that the subject is the home stadium used by the football club Oxford United.
- 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_69e2c4c725148190a4e41577c5cb409c |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:24 a.m.