Triple
T32655444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bamford & Martin Ltd. |
E834847
|
entity |
| Predicate | has marketing label |
P171270
|
FINISHED |
| Object | Aston-Martin |
E199432
|
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: Aston-Martin | Statement: [Bamford & Martin Ltd., has marketing label, Aston-Martin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has marketing label Context triple: [Bamford & Martin Ltd., has marketing label, Aston-Martin]
-
A.
isMarketingLabelFor
chosen
Indicates that a given label or phrase is used as the marketing designation or promotional name for a particular product, service, or entity.
-
B.
hasMarketingCategory
Indicates that an entity is associated with a specific marketing category or segment used for classification or targeting.
-
C.
hasMarketingElement
Indicates that one entity includes, is associated with, or makes use of a particular marketing-related component or feature.
-
D.
hasMarketingDescription
Indicates that an entity is associated with a textual marketing-oriented description used to promote or present it.
-
E.
hasMarketingIcon
Indicates that an entity is associated with, or represented by, a specific marketing-related icon or symbol.
- 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c77b504c8190aa225fad8f2cb2aa |
completed | May 3, 2026, 3:56 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3538eecd1081909dd2a5bf263312ee |
completed | June 19, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:08 a.m.