Triple
T3037321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volvo Cars |
E83041
|
entity |
| Predicate | announcedGoalYear |
P26643
|
FINISHED |
| Object | to sell only electric cars by 2030 |
—
|
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: to sell only electric cars by 2030 | Statement: [Volvo Cars, announcedGoalYear, to sell only electric cars by 2030]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedGoalYear Context triple: [Volvo Cars, announcedGoalYear, to sell only electric cars by 2030]
-
A.
hasGoalYear
chosen
Indicates that an entity is associated with a specific target year by which a goal or objective is intended to be achieved.
-
B.
claimedYear
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
-
C.
statedAsGoalFor
Indicates that something has been explicitly declared or identified as a goal for a particular entity or context.
-
D.
transitionYear
Indicates the specific year in which a change, shift, or transition from one state, condition, or phase to another occurs.
-
E.
declaredYear
Indicates the year in which something was formally announced, established, or proclaimed.
- 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_69ad8b2298908190a7cb4e9bdbf064d0 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b2cd4988190b52fe3616ecbe9ef |
completed | March 8, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.