Triple
T4055797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smolensk–Moscow Upland |
E84689
|
entity |
| Predicate | surfaceForm |
P1242
|
FINISHED |
| Object | low hills |
—
|
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: low hills | Statement: [Smolensk–Moscow Upland, surfaceForm, low hills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceForm Context triple: [Smolensk–Moscow Upland, surfaceForm, low hills]
-
A.
surfaceExpressionOf
Indicates that one entity is a specific surface-level manifestation or observable form of another underlying entity or concept.
-
B.
hasSurfaceForm
Indicates that an abstract concept, entity, or linguistic unit is realized or expressed in a specific textual or lexical form.
-
C.
surfaceState
Indicates the physical condition or status of a surface, such as its texture, cleanliness, damage, or treatment at a given time.
-
D.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
-
E.
surfaceType
chosen
Indicates the kind or classification of surface associated with an entity or interaction.
- 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbabec608190a35d39d3d03b928b |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.