Triple
T35400406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASU-57 |
E1023210
|
entity |
| Predicate | isLightVehicle |
P182928
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ASU-57, isLightVehicle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLightVehicle Context triple: [ASU-57, isLightVehicle, true]
-
A.
vehicleEligibility
Indicates whether a given vehicle satisfies the required conditions or criteria to be considered eligible for a specified purpose or program.
-
B.
vehicleStandard
Indicates that something complies with, or is defined according to, a specified vehicle-related standard or regulatory specification.
-
C.
intendedVehicleClass
Indicates that one entity is designed or specified to be used with, or is appropriate for, a particular class or category of vehicle.
-
D.
isTransportationType
Indicates that one entity functions as a mode or category of transportation for the other entity.
-
E.
intendedVehicle
Indicates that one entity is the vehicle that another entity plans or is meant to use.
- F. None of above. chosen
Provenance (4 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7953aeb18819089c35efbd10e6b00 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 3, 2026, 4:03 p.m.