Triple
T30954606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kate Moss |
E788639
|
entity |
| Predicate | hasCoverAppearanceOn |
P50487
|
FINISHED |
| Object | British Vogue |
E39386
|
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: British Vogue | Statement: [Kate Moss, hasCoverAppearanceOn, British Vogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoverAppearanceOn Context triple: [Kate Moss, hasCoverAppearanceOn, British Vogue]
-
A.
hasCoverType
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
B.
hasCoverFeature
chosen
Indicates that one entity serves as a prominent or featured element on the cover of another entity (such as a publication, product, or media item).
-
C.
isCover
Indicates that one entity functions as a protective or concealing layer over another entity.
-
D.
containsCoverOf
Indicates that one entity includes within it a cover or covering representation of another entity.
-
E.
hasCoverName
Indicates that one entity uses or is known by an alternative, often secret or assumed, name in relation to another entity or context.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01b241f7308190bedb7522cb5dc069 |
completed | May 11, 2026, 10:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28e483a78c819085d94bacfb2d789e |
completed | June 10, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_6a01b19ff12c81908ee1b188b4a3e118 |
completed | May 11, 2026, 10:38 a.m. |
Created at: April 29, 2026, 8:53 p.m.