Triple
T35916635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knobs region of Kentucky |
E1038763
|
entity |
| Predicate | hillMorphology |
P169824
|
FINISHED |
| Object | conical |
—
|
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: conical | Statement: [Knobs region of Kentucky, hillMorphology, conical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hillMorphology Context triple: [Knobs region of Kentucky, hillMorphology, conical]
-
A.
hillProfile
chosen
Indicates the characteristic shape or contour of a hill as defined by its elevation changes over distance.
-
B.
hillType
Indicates the specific classification or category of a hill based on its form, characteristics, or context.
-
C.
isHill
Indicates that the subject entity is classified as a hill, i.e., a naturally raised area of land lower and less steep than a mountain.
-
D.
topographicalForm
Indicates the specific physical shape or configuration of the Earth's surface associated with an entity (such as whether it is a mountain, valley, plateau, etc.).
-
E.
containsHill
Indicates that one entity geographically includes or encompasses a hill within its area or boundaries.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaa69e2c8190aad5087427023959 |
completed | May 3, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:07 p.m.