Triple
T30394587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Stand |
E773178
|
entity |
| Predicate | isHomeStandOf |
P36076
|
FINISHED |
| Object | AFC Bournemouth supporters |
—
|
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: AFC Bournemouth supporters | Statement: [Main Stand, isHomeStandOf, AFC Bournemouth supporters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHomeStandOf Context triple: [Main Stand, isHomeStandOf, AFC Bournemouth supporters]
-
A.
homeFieldForALTeam
Indicates that a particular stadium or ballpark serves as the designated home field for a specific American League baseball team.
-
B.
isHomeFieldOf
chosen
Indicates that a particular location or venue serves as the primary home field or home ground for a specific team or organization.
-
C.
playsHomeGamesOn
Indicates that an entity regularly hosts its home games or matches at a specified location or venue.
-
D.
homeFieldForAllGames
Indicates that the specified location serves as the designated home field for all of the referenced entity’s games.
-
E.
ownedTeamHomeState
Indicates that the owning entity’s home or primary location is in the same state as the team’s home state.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f685ac63248190a51b9e0e6ed89dab |
completed | May 2, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:02 p.m.