Triple
T31336875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L-twin |
E799197
|
entity |
| Predicate | hasPackagingBenefit |
P2188
|
FINISHED |
| Object | allows compact longitudinal engine layout in motorcycles |
—
|
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: allows compact longitudinal engine layout in motorcycles | Statement: [L-twin, hasPackagingBenefit, allows compact longitudinal engine layout in motorcycles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPackagingBenefit Context triple: [L-twin, hasPackagingBenefit, allows compact longitudinal engine layout in motorcycles]
-
A.
hasBenefit
chosen
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
B.
hasPackagingLimit
Indicates that there is a maximum allowed quantity, size, or type of packaging associated with an item or transaction.
-
C.
hasBenefitType
Indicates that an entity is associated with a specific category or type of benefit it provides or receives.
-
D.
hasPerformancePackage
Indicates that an entity is equipped with or associated with a specific performance-enhancing package or upgrade.
-
E.
hasFictionalPackaging
Indicates that an item is presented or wrapped in packaging that is imaginary, simulated, or not used in real-world distribution.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: April 29, 2026, 9:16 p.m.