Triple
T4303373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Rock Ridge State Park |
E99893
|
entity |
| Predicate | geologicFeature |
P4015
|
FINISHED |
| Object | traprock ridge |
—
|
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: traprock ridge | Statement: [West Rock Ridge State Park, geologicFeature, traprock ridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologicFeature Context triple: [West Rock Ridge State Park, geologicFeature, traprock ridge]
-
A.
geologicalFormation
chosen
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
B.
geographicalNature
Indicates the natural geographic characteristics or physical landscape type associated with a place or region.
-
C.
geologicType
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
-
D.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
E.
geologicalFormationProcess
Indicates the natural geological process or set of processes by which a particular geological formation came into existence.
- 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_69b345528ebc8190b5abc7e95094792d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350b792608190ac778b79c740256a |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b347ff45cc8190b0cc335a94cc3d73 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.