Triple
T3102737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW 3 Series |
E64756
|
entity |
| Predicate | productionEndForE90 |
P4160
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [BMW 3 Series, productionEndForE90, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionEndForE90 Context triple: [BMW 3 Series, productionEndForE90, 2013]
-
A.
productionEnd
chosen
Indicates that a production process, activity, or run has come to its completion or final stopping point.
-
B.
thirdGenerationEnd
Indicates that a third generation in a sequence, lineage, or process has reached its endpoint or conclusion.
-
C.
assembledNearEndOf
Indicates that one entity is put together or constructed in close proximity to the endpoint or final section of another entity.
-
D.
endTimeNinthCircuit
Indicates the time at which an event, action, or process concludes within the context or jurisdiction of the Ninth Circuit.
-
E.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
- 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_69ad857dc98481909e585dc3372e3ed5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada26df128819086541db7680c8c24 |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df06ed88190809f0683122caa5a |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:03 p.m.