Triple
T36835713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VK 45.01 (H) |
E910265
|
entity |
| Predicate | competitorDesign |
P193095
|
FINISHED |
| Object | Porsche Tiger |
—
|
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: Porsche Tiger | Statement: [VK 45.01 (H), competitorDesign, Porsche Tiger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitorDesign Context triple: [VK 45.01 (H), competitorDesign, Porsche Tiger]
-
A.
designedForCompetition
Indicates that something was intentionally created or configured to be used in a competitive context or event.
-
B.
competitorCategory
Indicates that two entities operate in the same competitive category or market segment, positioning them as rivals within that domain.
-
C.
designCompetitionWonBy
Indicates that a particular design competition was won by a specified participant or entity.
-
D.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
E.
competesWith
Indicates that two entities are in rivalry or opposition, each striving to outperform or gain advantage over the other in the same domain or objective.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: May 3, 2026, 4:13 p.m.