Triple
T36884139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VK 30.02 (M) |
E911562
|
entity |
| Predicate | competitorDesigner |
P193159
|
FINISHED |
| Object | Daimler-Benz |
—
|
NE NERFINISHED |
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: Daimler-Benz | Statement: [VK 30.02 (M), competitorDesigner, Daimler-Benz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitorDesigner Context triple: [VK 30.02 (M), competitorDesigner, Daimler-Benz]
-
A.
competitorDesign
Indicates that one entity has designed or created something that competes with a design or product of another entity.
-
B.
competitorOwner
Indicates that one entity owns or controls a business or asset that competes in the same market or domain as another entity’s business or asset.
-
C.
winnerDesignerBrand
Indicates that a particular designer brand has won a specified competition, award, or contest.
-
D.
designerAlias
Indicates that one name or label is used as an alternative alias for a designer.
-
E.
partnerInCompetition
Indicates that two or more entities are collaborating as partners or teammates within the same competitive event or context.
- F. None of above. chosen
Provenance (4 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: May 3, 2026, 4:13 p.m.