Triple
T20627889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guildford Spectrum Ice Rink |
E506867
|
entity |
| Predicate | isPartOfComplexType |
P72072
|
FINISHED |
| Object | multi-sport leisure complex |
—
|
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-sport leisure complex | Statement: [Guildford Spectrum Ice Rink, isPartOfComplexType, multi-sport leisure complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfComplexType Context triple: [Guildford Spectrum Ice Rink, isPartOfComplexType, multi-sport leisure complex]
-
A.
partOfComplexType
chosen
Indicates that an entity functions as a component or member within a larger, composite structure or complex type.
-
B.
isPartOfType
Indicates that one type or category is a constituent or subset within a larger, encompassing type or category.
-
C.
hasComplex
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with another entity.
-
D.
containsCompoundType
Indicates that one entity includes or is composed of another entity of a specified compound type.
-
E.
isComposite
Indicates that an entity is made up of multiple components or parts combined into a single whole.
- 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6abe645888190b639ebedc5b3041a |
completed | April 20, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
Created at: April 16, 2026, 11:42 a.m.