Triple
T32608695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lohner-Porsche Mixte Hybrid |
E833593
|
entity |
| Predicate | basedOnEarlierDesign |
P7125
|
FINISHED |
| Object | Lohner-Porsche electric car |
—
|
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: Lohner-Porsche electric car | Statement: [Lohner-Porsche Mixte Hybrid, basedOnEarlierDesign, Lohner-Porsche electric car]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnEarlierDesign Context triple: [Lohner-Porsche Mixte Hybrid, basedOnEarlierDesign, Lohner-Porsche electric car]
-
A.
basedOnDesignBy
Indicates that something is created, developed, or structured according to the design conceived or produced by a specified entity.
-
B.
previouslyBasedOn
Indicates that something was formerly derived from, adapted from, or dependent on another source, but is no longer based on it in its current state.
-
C.
isBasedOn
chosen
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
-
D.
hasBasedOn
Indicates that one entity is derived from, inspired by, or developed using another entity as its source or foundation.
-
E.
previousDesignFeature
Indicates that one design feature precedes another in a sequence or earlier version of a design.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: May 1, 2026, 1:05 a.m.