Triple
T14094699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW iX1 |
E339222
|
entity |
| Predicate | functionalSuccessorTo |
P23638
|
FINISHED |
| Object | BMW i3 as entry-level BMW EV |
—
|
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: BMW i3 as entry-level BMW EV | Statement: [BMW iX1, functionalSuccessorTo, BMW i3 as entry-level BMW EV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionalSuccessorTo Context triple: [BMW iX1, functionalSuccessorTo, BMW i3 as entry-level BMW EV]
-
A.
successorFrom
Indicates that one entity directly follows or comes after another in an ordered sequence or progression.
-
B.
isSuccessorTo
chosen
Indicates that one entity directly follows another in an ordered sequence, coming immediately after it.
-
C.
successorFunction
Indicates the relationship where one entity is defined as the immediate next or following element in a sequence or ordered set relative to another.
-
D.
successorInstanceOf
Indicates that one entity is a later or updated instance of another, preserving a continuity or versioned succession between them.
-
E.
successorDeterminedBy
Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fb7fb3c819083266dbe7e93aaff |
completed | April 14, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.