Triple
T38056949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Klassieker |
E950230
|
entity |
| Predicate | secondClubStadium |
P38843
|
FINISHED |
| Object | Stadion Feijenoord |
—
|
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: Stadion Feijenoord | Statement: [De Klassieker, secondClubStadium, Stadion Feijenoord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondClubStadium Context triple: [De Klassieker, secondClubStadium, Stadion Feijenoord]
-
A.
secondaryStadium
chosen
Indicates that an entity serves as an additional or backup stadium associated with another primary stadium or team.
-
B.
neighbouringStadium
Indicates that one stadium is located adjacent to or very close to another stadium.
-
C.
parentClubStadium
Indicates that a stadium serves as the home venue associated with a particular parent club.
-
D.
mainStadium
Indicates that a particular stadium serves as the primary or home stadium associated with an entity (such as a team, club, or organization).
-
E.
finalHostStadiumClub
Indicates that a particular stadium club serves as the host venue for the final match or event in a competition or series.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffcb5536d88190bfc2e00b854cacfb |
completed | May 10, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69ffc900c2a081909dea04aa60566923 |
completed | May 9, 2026, 11:53 p.m. |
Created at: May 3, 2026, 4:21 p.m.