Triple
T1756235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Littorina Sea |
E38554
|
entity |
| Predicate | hasMaximumExtent |
P22930
|
FINISHED |
| Object | larger than modern 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: larger than modern Baltic Sea | Statement: [Littorina Sea, hasMaximumExtent, larger than modern Baltic Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumExtent Context triple: [Littorina Sea, hasMaximumExtent, larger than modern Baltic Sea]
-
A.
maximumExtent
chosen
Indicates the greatest or furthest degree, size, or range to which something can extend or apply within a given context.
-
B.
hasApproximateExtent
Indicates that one entity has a spatial, temporal, or quantitative extent that is only roughly or approximately specified rather than exact.
-
C.
hasMaximumValue
Indicates that one value in a set is the greatest or highest possible according to a specified criterion.
-
D.
hasMaximumDepth
Indicates that an entity possesses a greatest or limiting depth value beyond which it does not extend.
-
E.
hasApproximateMaximumWidth
Indicates that an entity’s maximum width is known only approximately, rather than as an exact value.
- 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_69a8862bdb2081908aefe831c8aa8017 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aba6a63f588190b53b39c6b97d74f4 |
completed | March 7, 2026, 4:16 a.m. |
| PD | Predicate disambiguation | batch_69aa61c7ef4c8190abec87c96a787d82 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.