Triple
T3037298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volvo Cars |
E83041
|
entity |
| Predicate | brand |
P1500
|
FINISHED |
| Object | Volvo |
E142854
|
NE 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: Volvo | Statement: [Volvo Cars, brand, Volvo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Volvo Context triple: [Volvo Cars, brand, Volvo]
-
A.
Volvo Cars
Volvo Cars is a Swedish automotive manufacturer known for its focus on safety, practical design, and premium vehicles.
-
B.
Volvo Group
chosen
Volvo Group is a Swedish multinational manufacturing company best known for producing trucks, buses, construction equipment, and marine and industrial engines.
-
C.
Scania
Scania is a Swedish manufacturer renowned for its heavy trucks, buses, and industrial and marine engines.
-
D.
Scania
Scania is a historical province in southern Sweden known for its fertile farmland, coastal landscapes, and former status as part of Denmark.
-
E.
Saab Automobile
Saab Automobile was a Swedish car manufacturer known for its innovative engineering, turbocharged engines, and distinctive, safety-focused designs.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1f86cfcac81908122f1afd79ce29a |
completed | March 11, 2026, 11:19 p.m. |
Created at: March 8, 2026, 3:01 p.m.