Triple
T38057077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Stadionclub |
E950233
|
entity |
| Predicate | refersToStadium |
P80805
|
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 Stadionclub, refersToStadium, Stadion Feijenoord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToStadium Context triple: [De Stadionclub, refersToStadium, Stadion Feijenoord]
-
A.
stadiumFor
Indicates that a particular stadium serves as the designated home or primary venue for a specific team, event, or organization.
-
B.
appliesToStadiumName
Indicates that something is relevant or specifically associated with the name of a stadium.
-
C.
containsStadium
Indicates that a location or area includes a stadium within its boundaries or premises.
-
D.
associatedStadiums
chosen
Indicates that there is a relationship linking an entity to one or more stadiums with which it is connected or affiliated.
-
E.
associatedWithStadiumLocation
Indicates a relationship where an entity is connected or linked to the location of a specific 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fef112398081909237c3872345968b |
completed | May 9, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69feefb14ec08190ab401987d8c84a23 |
completed | May 9, 2026, 8:26 a.m. |
Created at: May 3, 2026, 4:21 p.m.