Triple
T13093184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Helens R.F.C. |
E310514
|
entity |
| Predicate | primaryKitDesign |
P108006
|
FINISHED |
| Object | white shirt with red vee |
—
|
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: white shirt with red vee | Statement: [St Helens R.F.C., primaryKitDesign, white shirt with red vee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryKitDesign Context triple: [St Helens R.F.C., primaryKitDesign, white shirt with red vee]
-
A.
traditionalKit
Indicates that an entity is a conventional or customary set of tools, equipment, or components used together for a particular purpose.
-
B.
kitType
Indicates the specific category or configuration of a kit associated with an entity or activity.
-
C.
primaryProduct
Indicates that one entity is the main or most important product associated with, produced by, or offered by another entity.
-
D.
primaryEquipment
Indicates that one entity serves as the main or most important piece of equipment used by another entity.
-
E.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
- F. None of above. chosen
Provenance (4 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9813cd1b881909871a318fdd60672 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98114a6508190b1e8e018bb5a068c |
completed | April 10, 2026, 11 p.m. |
Created at: April 9, 2026, 9:03 p.m.