Triple
T17217513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major Boothroyd |
E417889
|
entity |
| Predicate | notableGadgetsProvidedTo |
P66036
|
FINISHED |
| Object | Aston Martin DB5 modifications |
—
|
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: Aston Martin DB5 modifications | Statement: [Major Boothroyd, notableGadgetsProvidedTo, Aston Martin DB5 modifications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGadgetsProvidedTo Context triple: [Major Boothroyd, notableGadgetsProvidedTo, Aston Martin DB5 modifications]
-
A.
notableGadget
Indicates that an entity is a gadget that is recognized as notable, significant, or widely known in some context.
-
B.
notableProduct
Indicates that a product is especially significant, prominent, or well-known in relation to the associated entity.
-
C.
notableRelic
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
-
D.
hasGadget
chosen
Indicates that an entity possesses, uses, or is equipped with a particular gadget.
-
E.
typicalGadgets
Indicates that the associated items are commonly used or standard gadgets typically found or expected in a given context.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dda6e6c81908dd96f653cd2cba0 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.