Triple
T34470430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moldanubicum |
E884891
|
entity |
| Predicate | hasTectonicBoundaryWith |
P179421
|
FINISHED |
| Object | Saxothuringian Zone |
—
|
NE NERFINISHED |
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: Saxothuringian Zone | Statement: [Moldanubicum, hasTectonicBoundaryWith, Saxothuringian Zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTectonicBoundaryWith Context triple: [Moldanubicum, hasTectonicBoundaryWith, Saxothuringian Zone]
-
A.
tectonicPlateBoundaryRelation
chosen
Indicates a spatial or geological relationship between tectonic plates at their boundary, such as where they meet, interact, or move relative to each other.
-
B.
locatedOnTectonicBoundary
Indicates that one entity is situated directly on or along the tectonic plate boundary associated with another entity.
-
C.
plateBoundaryBetween
Indicates a geological relationship where a boundary exists between two tectonic plates.
-
D.
geographicallyBorders
Indicates that two geographic entities share a common boundary or border.
-
E.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 1, 2026, 2:01 a.m.