Triple
T8189290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Wales Challenge Cup |
E191263
|
entity |
| Predicate | spectatorSetting |
P31261
|
FINISHED |
| Object | riverside enclosures |
—
|
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: riverside enclosures | Statement: [Prince of Wales Challenge Cup, spectatorSetting, riverside enclosures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectatorSetting Context triple: [Prince of Wales Challenge Cup, spectatorSetting, riverside enclosures]
-
A.
spectatorType
Indicates the role or category of a spectator in relation to an event or activity.
-
B.
spectatorProfile
Indicates a relationship where one entity serves as or defines the viewing or audience-oriented characteristics, preferences, or behavior profile of another entity.
-
C.
spectatorRestrictions
Indicates limitations, conditions, or rules governing who may be present as spectators and under what circumstances.
-
D.
hasSpectators
Indicates that an event, activity, or occurrence is being watched or attended by one or more spectators.
-
E.
spectatorAreaType
chosen
Indicates the specific kind or category of area designated for spectators in a venue or event setting.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4da0e1288190b9c7c1d3b9a98830 |
completed | March 31, 2026, 4:29 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:41 p.m.