Triple
T37545542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jo Malone London |
E933454
|
entity |
| Predicate | hasSignatureNoteFamily |
P197078
|
FINISHED |
| Object | citrus |
—
|
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: citrus | Statement: [Jo Malone London, hasSignatureNoteFamily, citrus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignatureNoteFamily Context triple: [Jo Malone London, hasSignatureNoteFamily, citrus]
-
A.
hasSignatureVisualStyle
Indicates that an entity is characterized by a distinctive and recognizable visual style that sets it apart from others.
-
B.
hasSignatureTribe
Indicates that an entity has a primary or characteristic association with a particular tribe.
-
C.
hasSignatureConcept
Indicates that something is associated with or characterized by a defining concept that uniquely represents its core meaning or identity.
-
D.
hasSignatureRole
Indicates that an entity holds a primary, defining, or officially recognized role within a given context or relationship.
-
E.
hasSignaturePhrase
Indicates that an entity (such as a person or character) is associated with a distinctive, repeatedly used phrase that is characteristically theirs.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69fe7663b5bc81909524c40d3a172512 |
completed | May 8, 2026, 11:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.