Triple
T16180607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honda C70 |
E392672
|
entity |
| Predicate | hasLicenseCategory |
P19269
|
FINISHED |
| Object | small-displacement motorcycle |
—
|
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: small-displacement motorcycle | Statement: [Honda C70, hasLicenseCategory, small-displacement motorcycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLicenseCategory Context triple: [Honda C70, hasLicenseCategory, small-displacement motorcycle]
-
A.
hasDriverCategory
Indicates that an entity (such as a vehicle or driving role) is associated with a specific driver category or license class.
-
B.
hasLicense
Indicates that an entity possesses a valid authorization or permit, typically granted by an authority, to perform a specific activity or use something.
-
C.
typeOfLicense
chosen
Indicates the specific kind or category of license associated with an entity.
-
D.
vehicleRegistrationCategory
Indicates the classification or type of registration assigned to a vehicle under a specific regulatory or administrative scheme.
-
E.
hasDrivenInCategory
Indicates that an entity has previously driven or operated a vehicle within a specified driving category or classification.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205c92b48190b7125dbbcff3662e |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.