Triple
T1052659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltic Ice Lake |
E22733
|
entity |
| Predicate | maximumExtent |
P22930
|
FINISHED |
| Object | area of present-day northern Baltic Sea |
—
|
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: area of present-day northern Baltic Sea | Statement: [Baltic Ice Lake, maximumExtent, area of present-day northern Baltic Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumExtent Context triple: [Baltic Ice Lake, maximumExtent, area of present-day northern Baltic Sea]
-
A.
maximumExtentFromBaseline
Indicates the greatest distance or deviation of something from a defined baseline reference.
-
B.
maximumIntensity
Indicates the greatest level or strength that a quantity, effect, or signal can reach within a given context.
-
C.
maximumCapacity
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
D.
verticalExtent
Indicates the total height or vertical span of an entity or region from its lowest to highest point.
-
E.
maximumVolumeSize
Indicates the largest allowable size or capacity that a volume can have within a given system or context.
- 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8b644088190a1f0f00f97941298 |
completed | March 1, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69a4b731e25c8190b5ea8466648c2c9a |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7da38888190a118ef20ce4ae9aa |
completed | March 1, 2026, 10:04 p.m. |
Created at: March 1, 2026, 7:42 p.m.