Triple
T15729255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Mashu |
E381297
|
entity |
| Predicate | hasNoSettlementOnShore |
P57254
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lake Mashu, hasNoSettlementOnShore, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoSettlementOnShore Context triple: [Lake Mashu, hasNoSettlementOnShore, true]
-
A.
hasSettlementOnUSSide
Indicates that a settlement is located on the United States side of a border or boundary.
-
B.
hasSettlementOnBanks
chosen
Indicates that a settlement is located on or along the banks of a geographic feature such as a river, lake, or coastline.
-
C.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
D.
hasSubsettlement
Indicates that one settlement includes another, smaller settlement as a subordinate or component part.
-
E.
isSettlement
Indicates that the subject entity functions as a human-inhabited place or community, such as a town, village, or city.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb4cc0081909efe330339474017 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.