Triple
T12758603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hickory Run State Park |
E304924
|
entity |
| Predicate | hasNotableGeology |
P14413
|
FINISHED |
| Object | periglacial boulder field |
—
|
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: periglacial boulder field | Statement: [Hickory Run State Park, hasNotableGeology, periglacial boulder field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableGeology Context triple: [Hickory Run State Park, hasNotableGeology, periglacial boulder field]
-
A.
hasGeologicalSignificance
chosen
Indicates that something possesses notable importance or relevance within a geological context, such as Earth’s structure, history, or processes.
-
B.
hasGeologicalNature
Indicates that something possesses a specific geological character, composition, or formation type.
-
C.
surfaceGeologyKnown
Indicates that the composition or characteristics of an entity’s surface geology have been determined or are known.
-
D.
hasNotableFossilSite
Indicates that an entity contains or is associated with a fossil site recognized as significant or noteworthy.
-
E.
hasComplexGeology
Indicates that an entity possesses geologic features or structure that are intricate, varied, or highly heterogeneous rather than simple or uniform.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8d3eb08190ae998df5cc6d9ba6 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:27 p.m.