Triple
T17805825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Komering people |
E444554
|
entity |
| Predicate | riverBasedSettlements |
P70982
|
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: [Komering people, riverBasedSettlements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverBasedSettlements Context triple: [Komering people, riverBasedSettlements, true]
-
A.
riverineSettlement
chosen
Indicates that a settlement is located on or closely associated with the banks or course of a river.
-
B.
hasRiverBankSettlement
Indicates that a settlement is located on or directly adjacent to the bank of a river.
-
C.
hasTownOnRiver
Indicates that a town is situated on or directly adjacent to a particular river.
-
D.
hasMajorTownOnRiver
Indicates that a major town is located on and directly associated with a particular river.
-
E.
notableHumanSettlement
Indicates that a location is recognized as a significant or noteworthy human settlement, such as a city, town, or village.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4880385b48190b8dea0f05dfa1300 |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:14 a.m.