Triple
T2920193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devil’s Beef Tub |
E78700
|
entity |
| Predicate | hasTopographicCharacter |
P12436
|
FINISHED |
| Object | steep-sided |
—
|
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-sided | Statement: [Devil’s Beef Tub, hasTopographicCharacter, steep-sided]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTopographicCharacter Context triple: [Devil’s Beef Tub, hasTopographicCharacter, steep-sided]
-
A.
topographyBasedOn
Indicates that the topographical characteristics of one entity are derived from, determined by, or modeled using the topography of another entity.
-
B.
topographicMap
Indicates a mapping relationship where a representation shows the physical terrain features and elevation contours of a geographic area.
-
C.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
D.
topographicIsolation
Indicates the distance from a geographic feature to the nearest point of equal or greater elevation, expressing how isolated it is from higher terrain.
-
E.
hasGeographyCharacteristic
chosen
Indicates that an entity possesses a specific geographical feature, property, or attribute.
- 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_69ad8b0c2ad081909ff87050ae542bb9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:54 p.m.