Triple
T33723696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BC |
E864084
|
entity |
| Predicate | regulatesVehicleCategory |
P23423
|
FINISHED |
| Object | civilian vehicles |
—
|
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: civilian vehicles | Statement: [BC, regulatesVehicleCategory, civilian vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesVehicleCategory Context triple: [BC, regulatesVehicleCategory, civilian vehicles]
-
A.
vehicleRegistrationCategory
Indicates the classification or type of registration assigned to a vehicle under a specific regulatory or administrative scheme.
-
B.
vehicleClassDriven
Indicates that an entity drives or operates a vehicle belonging to a particular vehicle class or category.
-
C.
appliedToVehicleType
chosen
Indicates that something (such as a rule, restriction, or condition) is specifically applicable to a particular type or category of vehicle.
-
D.
hasDriverCategory
Indicates that an entity (such as a vehicle or driving role) is associated with a specific driver category or license class.
-
E.
intendedVehicleClass
Indicates that one entity is designed or specified to be used with, or is appropriate for, a particular class or category of vehicle.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 1, 2026, 1:44 a.m.