Triple
T32606841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Side Saddle |
E833541
|
entity |
| Predicate | hasSalesCertificationRegion |
P115750
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [Side Saddle, hasSalesCertificationRegion, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSalesCertificationRegion Context triple: [Side Saddle, hasSalesCertificationRegion, United Kingdom]
-
A.
hasSalesCertification
Indicates that an entity possesses an official certification related to sales skills, knowledge, or qualifications.
-
B.
certifyingTerritory
chosen
Indicates the territory or jurisdiction within which an entity is authorized to issue or recognize a certification.
-
C.
isCertified
Indicates that an entity has been officially recognized as meeting specific standards or qualifications by an authorized body.
-
D.
issuerRegionServed
Indicates the geographic region or area that the issuer provides services to or operates within.
-
E.
salesCertificationContext
Indicates the contextual relationship in which a sales-related certification is obtained, applied, or relevant.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 1, 2026, 1:05 a.m.