Triple
T8235658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orcadian Basin |
E192397
|
entity |
| Predicate | depositionalEnvironmentIncludes |
P9688
|
FINISHED |
| Object | large lake system |
—
|
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: large lake system | Statement: [Orcadian Basin, depositionalEnvironmentIncludes, large lake system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depositionalEnvironmentIncludes Context triple: [Orcadian Basin, depositionalEnvironmentIncludes, large lake system]
-
A.
depositionalEnvironment
chosen
Indicates the natural setting or conditions under which sediments were originally deposited.
-
B.
geologyIncludes
Indicates that one geological entity contains, encompasses, or has as a component another geological entity.
-
C.
hasSedimentsThat
Indicates that one entity contains, includes, or is associated with specific sediments described by the related entity.
-
D.
hasSedimentaryBasin
Indicates that a geological region or area contains or is associated with a sedimentary basin.
-
E.
foundInGeologicSetting
Indicates that something occurs, is present, or has been discovered within a particular geological environment or context.
- 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb782a5e18819096235679f5a644a8 |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:46 p.m.