Triple
T32608520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamborghini 350 GT |
E833589
|
entity |
| Predicate | successorModelFamily |
P16897
|
FINISHED |
| Object | Lamborghini 400 GT 2+2 |
—
|
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: Lamborghini 400 GT 2+2 | Statement: [Lamborghini 350 GT, successorModelFamily, Lamborghini 400 GT 2+2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorModelFamily Context triple: [Lamborghini 350 GT, successorModelFamily, Lamborghini 400 GT 2+2]
-
A.
successorModel
chosen
Indicates that one model is the direct follow-up or replacement for another earlier model.
-
B.
successorEngineFamily
Indicates that one engine family directly follows and replaces another in a product or development lineage.
-
C.
successorFamily
Indicates that one family succeeds or follows another family in a lineage, role, position, or ownership.
-
D.
successorManufacturer
Indicates that one manufacturer has taken over, replaced, or continued the role or operations of another manufacturer as its successor.
-
E.
successorBodyStyleLine
Indicates that one body style line directly follows and replaces another in a sequence or product lineage.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff41645c548190b7cb4e53079b93ef |
completed | May 9, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69ff410aa33c8190869ba769ac2a93ce |
completed | May 9, 2026, 2:13 p.m. |
Created at: May 1, 2026, 1:05 a.m.