Triple
T17626813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orava-Nowy Targ Basin |
E429866
|
entity |
| Predicate | terrainForm |
P111759
|
FINISHED |
| Object | broad valley |
—
|
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: broad valley | Statement: [Orava-Nowy Targ Basin, terrainForm, broad valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terrainForm Context triple: [Orava-Nowy Targ Basin, terrainForm, broad valley]
-
A.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
B.
terrainIncludes
Indicates that a specified terrain area contains or encompasses another geographic or environmental feature within its boundaries.
-
C.
topographicalForm
chosen
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.).
-
D.
terrainSpecialization
Indicates a relationship where an entity is particularly adapted or optimized for operation, performance, or use within a specific type of terrain.
-
E.
terrainStyle
Indicates the characteristic type or pattern of terrain associated with an entity or location.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dbd122c8190a5db8c0088c81034 |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.