Triple
T7589778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TN |
E179704
|
entity |
| Predicate | vehicleCategoryCoverage |
P38809
|
FINISHED |
| Object | private 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: private vehicles | Statement: [TN, vehicleCategoryCoverage, private vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleCategoryCoverage Context triple: [TN, vehicleCategoryCoverage, private vehicles]
-
A.
vehiclePolicy
Indicates a relationship where a policy governs, regulates, or defines rules and conditions for the use, operation, or management of a vehicle.
-
B.
vehicleType
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
C.
typeOfCoverage
chosen
Indicates the specific kind or category of coverage that applies in a given context (such as insurance, service, or protection).
-
D.
vehicleRegistrationCategory
Indicates the classification or type of registration assigned to a vehicle under a specific regulatory or administrative scheme.
-
E.
vehicleStandard
Indicates that something complies with, or is defined according to, a specified vehicle-related standard or regulatory specification.
- 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_69c69f335248819093c1006f30513708 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9b615f481908b2fe7e8aaed81bc |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.