Triple
T29609236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Lama |
E754667
|
entity |
| Predicate | isUpriverSettlement |
P167506
|
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: [Long Lama, isUpriverSettlement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUpriverSettlement Context triple: [Long Lama, isUpriverSettlement, true]
-
A.
isWaterfrontSettlement
Indicates that a settlement is located directly adjacent to a body of water, such as a sea, lake, or river.
-
B.
hasSettlementOnRiver
Indicates that a settlement is located on or directly adjacent to a specific river.
-
C.
hasRiverBankSettlement
Indicates that a settlement is located on or directly adjacent to the bank of a river.
-
D.
isUrbanSettlementIn
Indicates that an urban settlement (such as a city or town) is located within a specified larger geographic or administrative area.
-
E.
riverineSettlement
Indicates that a settlement is located on or closely associated with the banks or course of a river.
- F. None of above. chosen
Provenance (4 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66dea375881909684db997861425c |
completed | May 2, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:27 p.m.