Triple
T4742639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radziejowa |
E105281
|
entity |
| Predicate | mountainRangeOrientation |
P58511
|
FINISHED |
| Object | east-west |
—
|
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: east-west | Statement: [Radziejowa, mountainRangeOrientation, east-west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainRangeOrientation Context triple: [Radziejowa, mountainRangeOrientation, east-west]
-
A.
mountainRange
Indicates that one entity is a mountain range that the other entity is part of, associated with, or located in.
-
B.
mountainRangeType
Indicates the classification or category of a mountain range based on its geological or geographical type.
-
C.
sourceMountainRange
Indicates that a river, stream, or similar feature originates from or has its source in a specified mountain range.
-
D.
shareMountainRange
Indicates that two geographic entities are located within or along the same mountain range.
-
E.
cliffOrientation
Indicates the directional facing or alignment of a cliff relative to a reference frame (e.g., compass direction or slope aspect).
- F. None of above. chosen
Provenance (4 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64a7153881909eac451fc7566d25 |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd637e19e081909e415544106c7835 |
completed | March 20, 2026, 3:10 p.m. |
Created at: March 20, 2026, 1:19 p.m.