Triple
T30325031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dungannon Swifts F.C. |
E771313
|
entity |
| Predicate | hasHomeGroundCapacityCategory |
P131254
|
FINISHED |
| Object | small stadium |
—
|
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: small stadium | Statement: [Dungannon Swifts F.C., hasHomeGroundCapacityCategory, small stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeGroundCapacityCategory Context triple: [Dungannon Swifts F.C., hasHomeGroundCapacityCategory, small stadium]
-
A.
hasHomeCapacityVenue
Indicates that a venue has a specified capacity for accommodating people or events as its home location.
-
B.
hasBallparkCapacityCategory
chosen
Indicates the classification of a ballpark’s seating capacity into a predefined size or capacity category.
-
C.
homeStadiumCapacity
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
D.
denotesHomeGroundOf
Indicates that a particular location serves as the primary home ground or home venue for a specified team, organization, or entity.
-
E.
homeArenaCapacity
Indicates the maximum number of spectators that can be accommodated in an entity’s home arena.
- 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 29, 2026, 7:52 p.m.