Triple
T30620738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OCR |
E779436
|
entity |
| Predicate | notableQualificationBrand |
P185928
|
FINISHED |
| Object | Cambridge Nationals |
E1923968
|
NE 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: Cambridge Nationals | Statement: [OCR, notableQualificationBrand, Cambridge Nationals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableQualificationBrand Context triple: [OCR, notableQualificationBrand, Cambridge Nationals]
-
A.
notableBrandElement
Indicates that one entity is a significant or distinguishing brand-related feature, component, or asset of another entity.
-
B.
hasBrandRole
Indicates that an entity holds a specific functional or organizational role in relation to a particular brand.
-
C.
notableWorkCertification
chosen
Indicates that a certification is a notable or significant work associated with an entity.
-
D.
hasNotableBrandAssociation
Indicates that there is a significant, recognizable, or influential brand linked or connected to the subject entity.
-
E.
hasBrandSpecialization
Indicates that an entity focuses on, is tailored to, or primarily serves a specific brand or set of brands.
- F. None of above.
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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2870e696e481909a5925977f72829f |
completed | June 9, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:27 p.m.