Triple
T11024042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moravo–Silesian Zone |
E260568
|
entity |
| Predicate | structuralPosition |
P9544
|
FINISHED |
| Object | eastern part of Bohemian Massif |
—
|
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: eastern part of Bohemian Massif | Statement: [Moravo–Silesian Zone, structuralPosition, eastern part of Bohemian Massif]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structuralPosition Context triple: [Moravo–Silesian Zone, structuralPosition, eastern part of Bohemian Massif]
-
A.
positioning
chosen
Indicates the spatial or contextual arrangement of one entity relative to another or within a given environment.
-
B.
segmentPositioning
Indicates how segments are arranged or ordered relative to one another within a larger structure or sequence.
-
C.
classPosition
Indicates the relative ordering or rank of an entity within a class, group, or sequence.
-
D.
hasSuperstructurePosition
Indicates the relative location or placement of a component or element within the superstructure of an object or system.
-
E.
subjectPosition
Indicates the spatial or logical position of a subject relative to a reference frame, context, or other entities.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797be9f148190a3a967bad5947496 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.