Triple
T37360296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KNVB |
E927557
|
entity |
| Predicate | usesStadiumAsHomeGround |
P47009
|
FINISHED |
| Object | Johan Cruijff ArenA for Netherlands national team matches |
—
|
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: Johan Cruijff ArenA for Netherlands national team matches | Statement: [KNVB, usesStadiumAsHomeGround, Johan Cruijff ArenA for Netherlands national team matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStadiumAsHomeGround Context triple: [KNVB, usesStadiumAsHomeGround, Johan Cruijff ArenA for Netherlands national team matches]
-
A.
stadiumUsedFor
Indicates that a particular stadium is used for a specific activity, event, or purpose.
-
B.
homeStadiumSituatedOn
Indicates that a team's home stadium is physically located on or within the grounds of a specified site or area.
-
C.
homeTeamStadiumUsed
Indicates that a particular stadium is used as the home venue by a specified home team.
-
D.
locatedAtStadiumOfClub
Indicates that something is situated in the stadium that belongs to or is used by a particular sports club.
-
E.
hostTeamStadium
chosen
Indicates that a particular team plays its home games at a specified stadium.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: May 3, 2026, 4:16 p.m.