Triple
T7192750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln Nautilus |
E167733
|
entity |
| Predicate | successorToNameplate |
P75668
|
FINISHED |
| Object | Lincoln MKX nameplate |
—
|
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: Lincoln MKX nameplate | Statement: [Lincoln Nautilus, successorToNameplate, Lincoln MKX nameplate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorToNameplate Context triple: [Lincoln Nautilus, successorToNameplate, Lincoln MKX nameplate]
-
A.
successorBranding
Indicates that one brand has replaced or continued another brand as its subsequent or updated identity.
-
B.
nicknameOfSuccessor
Indicates that one entity is a nickname or informal name used to refer to another entity that is its successor.
-
C.
successorNamesake
Indicates that one entity is named after another entity that precedes it, typically as its successor or continuation in name.
-
D.
successorLabel
Indicates that one entity is the direct successor or next in sequence to another entity, often inheriting its role, position, or label.
-
E.
successorUse
Indicates that one entity is used or applied as the subsequent or follow-up use of another entity in a sequence or lifecycle.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e901ea1481908a9e44f96dd4b553 |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e8b5f6508190af28e06a7959d717 |
completed | March 27, 2026, 8:29 p.m. |
Created at: March 27, 2026, 2:50 p.m.