Triple
T14716303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barn Bluff |
E345688
|
entity |
| Predicate | landformCharacteristic |
P102056
|
FINISHED |
| Object | steep cliffs |
—
|
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: steep cliffs | Statement: [Barn Bluff, landformCharacteristic, steep cliffs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landformCharacteristic Context triple: [Barn Bluff, landformCharacteristic, steep cliffs]
-
A.
physicalFeature
chosen
Indicates that one entity possesses or exhibits a particular physical characteristic or attribute.
-
B.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
C.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
D.
topographicalCategory
Indicates the type of landform or surface feature that characterizes the physical terrain associated with an entity.
-
E.
mountainFeature
Indicates that one entity is a notable physical or geographical feature associated with, located on, or forming part of a mountain.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98688f48190b2b19ce7aa06a6db |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.