Triple
T9819676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Pinos |
E238496
|
entity |
| Predicate | isCountyHighPointOf |
P27839
|
FINISHED |
| Object | Ventura County, California |
—
|
NE NERFINISHED |
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: Ventura County, California | Statement: [Mount Pinos, isCountyHighPointOf, Ventura County, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCountyHighPointOf Context triple: [Mount Pinos, isCountyHighPointOf, Ventura County, California]
-
A.
recognizedAsStateHighPointSince
Indicates that an entity has been officially acknowledged as the highest point of a state starting from a specified date or time.
-
B.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
C.
territorialPeak
Indicates the highest geographical point located within the territory or jurisdiction of a given entity.
-
D.
highestPointRegion
Indicates that one location is the highest point within a specified region.
-
E.
areaPeak
chosen
Indicates that a specified location or region is the highest point (peak) within a given area or spatial extent.
- 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_69ca84dfde1481909f47c286d715f892 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb2f74e348190be8e4394ae6fe3fe |
completed | April 2, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:31 p.m.