Triple
T6083779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunda Shelf |
E135585
|
entity |
| Predicate | seaLevelHistory |
P63416
|
FINISHED |
| Object | exposed as dry land during Pleistocene low sea levels |
—
|
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: exposed as dry land during Pleistocene low sea levels | Statement: [Sunda Shelf, seaLevelHistory, exposed as dry land during Pleistocene low sea levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaLevelHistory Context triple: [Sunda Shelf, seaLevelHistory, exposed as dry land during Pleistocene low sea levels]
-
A.
seaLevelCharacteristic
Indicates a characteristic, property, or attribute specifically related to sea level.
-
B.
emergedAboveSeaLevel
chosen
Indicates that something rose or became exposed above the surface of the sea from a previously submerged or lower position.
-
C.
seaDepth
Indicates the measured vertical distance from the sea surface down to the seafloor at a given location.
-
D.
deepestStationDepthMeters
Indicates the maximum depth, in meters, reached by any station associated with the subject.
-
E.
maximumDepthBelowSeaLevel
Indicates the greatest vertical distance an entity extends or reaches below sea level.
- 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c057877b448190aa12d2484102eeaa |
completed | March 22, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:11 p.m.