Triple
T18470967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milton End |
E451298
|
entity |
| Predicate | hasAwaySupportersSection |
P131777
|
FINISHED |
| Object | visiting 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: visiting supporters | Statement: [Milton End, hasAwaySupportersSection, visiting supporters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAwaySupportersSection Context triple: [Milton End, hasAwaySupportersSection, visiting supporters]
-
A.
hasBleacherSeating
Indicates that a venue or location is equipped with bleacher-style seating for spectators.
-
B.
hasGrandstandFeature
Indicates that something possesses or includes a grandstand-related feature or characteristic.
-
C.
supportsHomeMatchesOf
Indicates that one entity provides backing, resources, or assistance specifically for the home matches of another entity.
-
D.
supportsAwayMatchesOf
Indicates that one entity provides backing, resources, or endorsement specifically for the away matches played by another entity.
-
E.
supportersPresent
Indicates that one or more supporters are present at a given event, location, or context.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5305f428c81909980bd30d150e7dd |
completed | April 19, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:34 a.m.