Triple
T33243758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aston Martin Lagonda series |
E851036
|
entity |
| Predicate | usesNameplate |
P56036
|
FINISHED |
| Object | Lagonda |
—
|
NE NERFINISHED |
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: Lagonda | Statement: [Aston Martin Lagonda series, usesNameplate, Lagonda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNameplate Context triple: [Aston Martin Lagonda series, usesNameplate, Lagonda]
-
A.
introducedAsNameplate
chosen
Indicates that an entity is presented or displayed as a nameplate identifying another entity.
-
B.
usesBrandCharacter
Indicates that one entity employs or features another entity’s brand character (such as a mascot or branded persona) in its materials, products, or communications.
-
C.
usesNicknameIn
Indicates that one entity refers to another entity by a specific nickname within a particular context or setting.
-
D.
hasInsigniaWornBy
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
-
E.
usesNameDueTo
Indicates that one entity adopts or applies a particular name for another entity specifically because of some motivating reason, circumstance, or dependency.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:31 a.m.