Triple
T20922686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammersmith End |
E515254
|
entity |
| Predicate | hasHomeFansOnlySegregation |
P141693
|
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: [Hammersmith End, hasHomeFansOnlySegregation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeFansOnlySegregation Context triple: [Hammersmith End, hasHomeFansOnlySegregation, true]
-
A.
hasHomeFans
Indicates that a team, player, or participant is supported by fans located at their home venue or home location.
-
B.
hasAwaySupportersSection
Indicates that a venue or stadium includes a designated seating area specifically reserved for supporters of the visiting team.
-
C.
raceSegregationStatus
Indicates whether entities are separated, treated differently, or organized based on racial categories or distinctions.
-
D.
typeOfSegregationAddressed
Indicates the specific form or category of segregation that is being targeted, handled, or dealt with in a given context.
-
E.
segregationBasis
Indicates the criterion or characteristic used as the basis for separating or distinguishing one group or set from another.
- 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f64f767481909deccd77b50bf4ae |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53d22d08190bc17ed4bed53804a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:49 p.m.