Triple
T24624600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scandinavian Caledonides |
E609501
|
entity |
| Predicate | overthrustOnto |
P156786
|
FINISHED |
| Object | Baltic Craton |
—
|
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: Baltic Craton | Statement: [Scandinavian Caledonides, overthrustOnto, Baltic Craton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overthrustOnto Context triple: [Scandinavian Caledonides, overthrustOnto, Baltic Craton]
-
A.
thrust
Indicates a forceful forward push or drive exerted by one entity onto another or into a particular direction.
-
B.
over
Indicates that one entity is positioned higher than and extending across or above another entity, often covering or spanning it.
-
C.
overburden
Indicates that one entity places an excessive load, demand, or responsibility on another, beyond what it can reasonably handle.
-
D.
overtook
Indicates that one entity moved past and ahead of another that was previously in front, typically while both were in motion.
-
E.
overcomes
Indicates that one entity successfully prevails against, defeats, or gains control over another entity or opposing force.
- 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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:32 a.m.