Triple
T17630494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hitchin Town F.C. |
E429961
|
entity |
| Predicate | usesStadiumType |
P25179
|
FINISHED |
| Object | multi-purpose football ground |
—
|
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: multi-purpose football ground | Statement: [Hitchin Town F.C., usesStadiumType, multi-purpose football ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStadiumType Context triple: [Hitchin Town F.C., usesStadiumType, multi-purpose football ground]
-
A.
appliedToStadiumType
Indicates that something (such as a rule, condition, or attribute) is specifically applied to a particular type or category of stadium.
-
B.
hasStadiumUse
chosen
Indicates that one entity (typically a team, organization, or event) uses or is authorized to use a particular stadium for its activities or purposes.
-
C.
containsStadium
Indicates that a location or area includes a stadium within its boundaries or premises.
-
D.
hostStadiumType
Indicates the type or category of stadium that serves as the host venue for an event or activity.
-
E.
homeStadiumType
Indicates the type or classification of a venue that serves as a team's primary home stadium.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dc01b1c819099e3329cfb8cb77f |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.