Triple
T16837075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manas Lake |
E409310
|
entity |
| Predicate | locatedInGeologicRegion |
P19734
|
FINISHED |
| Object | inland basin |
—
|
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: inland basin | Statement: [Manas Lake, locatedInGeologicRegion, inland basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInGeologicRegion Context triple: [Manas Lake, locatedInGeologicRegion, inland basin]
-
A.
geologicalOriginRegion
Indicates the geographic region from which a geological feature, material, or formation originally derives.
-
B.
regionalGeologyContext
Indicates the broader geological setting or framework within which a specific geological feature, event, or observation occurs.
-
C.
foundInGeologicSetting
chosen
Indicates that something occurs, is present, or has been discovered within a particular geological environment or context.
-
D.
geologicalProvinceOf
Indicates that one entity is the geological province to which another entity (such as a region or feature) belongs or is classified.
-
E.
hasGeologicalProvince
Indicates that a geographic area or location is associated with, or belongs to, a specific geological province characterized by common geological features or history.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b34e080c8190bf7a236205b41db2 |
completed | April 18, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.