Triple
T28329560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swansea Stadium Management Company |
E717499
|
entity |
| Predicate | usesVenueName |
P78175
|
FINISHED |
| Object | Swansea.com Stadium |
—
|
NE NERFINISHED |
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: Swansea.com Stadium | Statement: [Swansea Stadium Management Company, usesVenueName, Swansea.com Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVenueName Context triple: [Swansea Stadium Management Company, usesVenueName, Swansea.com Stadium]
-
A.
usesVenues
chosen
Indicates that one entity makes use of or operates within specific venues or locations to carry out its activities or services.
-
B.
hasVenueName
Indicates that an entity has a specific name used to identify the venue where an event or activity takes place.
-
C.
homeVenueName
Indicates the name of the primary venue or location where an entity (such as a team, event, or organization) regularly hosts its home activities.
-
D.
usesVenueDesignedBy
Indicates that one entity makes use of a venue that was designed by another specified entity.
-
E.
hostVenueInstanceOf
Indicates that a specific host venue is an instance or concrete realization of a more general venue type or category.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 12:31 a.m.