Triple
T33007755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Stand |
E844555
|
entity |
| Predicate | homeSupporterEnd |
P175907
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [South Stand, homeSupporterEnd, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeSupporterEnd Context triple: [South Stand, homeSupporterEnd, true]
-
A.
homeSupportersSectionFor
Indicates that a particular seating section is designated for the home team's supporters at a sporting event or venue.
-
B.
isPrimaryHomeSupportEndFor
Indicates the point in time or condition at which an entity’s role as the main provider of home-based support for another entity ends.
-
C.
hasHomeSupport
Indicates that an entity receives assistance, backing, or favorable conditions from its home environment or local supporters.
-
D.
supportEndedIn
Indicates that a previously existing support relationship between entities has come to an end at a specific point in time.
-
E.
homeStandOf
Indicates that a particular venue or location serves as the primary home stadium or home ground for a sports team or organization.
- F. None of above. chosen
Provenance (4 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d749e7f081909c8196898c4191ad |
completed | May 3, 2026, 5:04 a.m. |
Created at: May 1, 2026, 1:23 a.m.