Triple
T27687243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche Tiger VK 45.01(P) |
E698063
|
entity |
| Predicate | intendedWeightClass |
P8068
|
FINISHED |
| Object | approximately 45 tonnes |
—
|
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: approximately 45 tonnes | Statement: [Porsche Tiger VK 45.01(P), intendedWeightClass, approximately 45 tonnes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedWeightClass Context triple: [Porsche Tiger VK 45.01(P), intendedWeightClass, approximately 45 tonnes]
-
A.
intendedUserWeightClass
Indicates the weight category or range for which a user is specifically targeted or intended.
-
B.
weightClass
chosen
Indicates the categorical grouping of an entity based on its weight range or mass classification.
-
C.
intendedWeight
Indicates the target or desired weight that an entity is meant or planned to have, rather than its current actual weight.
-
D.
allowsWeightClasses
Indicates that one entity permits or supports the use of defined weight categories for another entity or within a given context.
-
E.
weightClassAlternativeName
Indicates that one weight class is referred to by an alternative name or label.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 27, 2026, 2:50 p.m.