Triple
T35300375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friese Derby |
E1019486
|
entity |
| Predicate | homeStadiumOfSCHeerenveen |
P47009
|
FINISHED |
| Object | Abe Lenstra Stadion |
—
|
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: Abe Lenstra Stadion | Statement: [Friese Derby, homeStadiumOfSCHeerenveen, Abe Lenstra Stadion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStadiumOfSCHeerenveen Context triple: [Friese Derby, homeStadiumOfSCHeerenveen, Abe Lenstra Stadion]
-
A.
homeStadiumSituatedOn
Indicates that a team's home stadium is physically located on or within the grounds of a specified site or area.
-
B.
homeStadiumFeatureOf
Indicates that a stadium serves as the designated home venue or primary hosting facility for a particular team, club, or organization.
-
C.
homeStadium
Indicates that a particular stadium serves as the primary venue where a sports team plays its home games.
-
D.
hostTeamStadium
chosen
Indicates that a particular team plays its home games at a specified stadium.
-
E.
homeStadiumLocatedIn
Indicates that the home stadium of a sports team or organization is geographically situated within a specified location or region.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7902142ec8190b515088fb68e7a3e |
completed | May 3, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.