Triple
T28341738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotus Evija |
E717831
|
entity |
| Predicate | plannedProductionUnits |
P51752
|
FINISHED |
| Object | 130 |
—
|
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: 130 | Statement: [Lotus Evija, plannedProductionUnits, 130]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedProductionUnits Context triple: [Lotus Evija, plannedProductionUnits, 130]
-
A.
plannedProductionVersion
Indicates that a specific version of a product or item is scheduled or intended to be produced in the future.
-
B.
numberPlanned
chosen
Indicates that a specific quantity has been scheduled or intended for a future action or allocation.
-
C.
totalProduction
Indicates the overall quantity of goods, services, or output produced by an entity or system over a specified period or within a defined scope.
-
D.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
E.
productionCapacity
Indicates the maximum amount of output an entity can produce within a given time or resource constraint.
- 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 12:40 a.m.