Triple
T11118279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnson Valley Off-Highway Vehicle Area |
E262950
|
entity |
| Predicate | vehicleTypeAllowed |
P23423
|
FINISHED |
| Object | 4x4 trucks |
—
|
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: 4x4 trucks | Statement: [Johnson Valley Off-Highway Vehicle Area, vehicleTypeAllowed, 4x4 trucks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleTypeAllowed Context triple: [Johnson Valley Off-Highway Vehicle Area, vehicleTypeAllowed, 4x4 trucks]
-
A.
vehicleEligibility
Indicates whether a given vehicle satisfies the required conditions or criteria to be considered eligible for a specified purpose or program.
-
B.
vehicleType
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
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.
vehicleFamily
Indicates that two vehicles belong to the same family or category based on shared design, platform, or lineage.
-
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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79af6fe448190b042c2e77b855b05 |
completed | April 9, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.