Triple
T38056948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Klassieker |
E950230
|
entity |
| Predicate | firstClubStadium |
P2696
|
FINISHED |
| Object | Johan Cruijff Arena |
E272032
|
NE 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: Johan Cruijff Arena | Statement: [De Klassieker, firstClubStadium, Johan Cruijff Arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstClubStadium Context triple: [De Klassieker, firstClubStadium, Johan Cruijff Arena]
-
A.
parentClubStadium
Indicates that a stadium serves as the home venue associated with a particular parent club.
-
B.
locatedAtStadiumOfClub
Indicates that something is situated in the stadium that belongs to or is used by a particular sports club.
-
C.
homeStadiumOf
chosen
Indicates that a particular stadium serves as the primary home venue for a specific sports team or organization.
-
D.
finalHostStadiumClub
Indicates that a particular stadium club serves as the host venue for the final match or event in a competition or series.
-
E.
homeGroundOfAssociatedClub
Indicates that a particular venue or ground serves as the designated home location for an associated sports club.
- F. None of above.
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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a416801f21081908f14feb1b2ae0253 |
completed | June 28, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.