Triple
T21112595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saalian glaciation |
E520209
|
entity |
| Predicate | regionalTermUsedIn |
P14444
|
FINISHED |
| Object | German stratigraphy |
—
|
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: German stratigraphy | Statement: [Saalian glaciation, regionalTermUsedIn, German stratigraphy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalTermUsedIn Context triple: [Saalian glaciation, regionalTermUsedIn, German stratigraphy]
-
A.
regionallyKnownAs
chosen
Indicates that an entity is known by a particular name or designation within a specific geographic region.
-
B.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
C.
usedInRegion
Indicates that something is utilized or applied within a specific geographic or administrative region.
-
D.
usesTermForTerritory
Indicates that one entity employs a specific term or label to refer to a particular territory or geographic area.
-
E.
modernUsageRegion
Indicates the geographic region where something is currently or most commonly used in modern times.
- 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_69e0b509a318819092fbbcb21d1fe603 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72103b3888190a19e9a40f01fb439 |
completed | April 21, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:54 p.m.