Triple
T20065049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnson Valley, California |
E499585
|
entity |
| Predicate | offRoadAreaSize |
P138563
|
FINISHED |
| Object | one of the largest OHV areas in the United States |
—
|
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: one of the largest OHV areas in the United States | Statement: [Johnson Valley, California, offRoadAreaSize, one of the largest OHV areas in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offRoadAreaSize Context triple: [Johnson Valley, California, offRoadAreaSize, one of the largest OHV areas in the United States]
-
A.
arenaLength
Indicates that a specified arena has a particular length measurement.
-
B.
hasAreaRange
Indicates that something’s area falls within a specified minimum-to-maximum range.
-
C.
arenaWidth
Indicates the width dimension of an arena in a given context or representation.
-
D.
hasOffRoadSections
Indicates that a route, path, or roadway includes segments that are not on standard paved or main roads, such as trails, dirt tracks, or other off-road portions.
-
E.
fieldSize
Indicates the magnitude or dimensions of a field associated with an entity or context.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e663787190819096b2b78b38c1bf12 |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:39 p.m.