Triple
T31805119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melawi Regency |
E811850
|
entity |
| Predicate | hasRiverineCulture |
P168070
|
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: [Melawi Regency, hasRiverineCulture, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverineCulture Context triple: [Melawi Regency, hasRiverineCulture, true]
-
A.
hasRiverCulture
chosen
Indicates that an entity possesses cultural practices, traditions, or ways of life that are strongly shaped by its relationship with a river or river system.
-
B.
hasRiverValley
Indicates that one location contains, includes, or is characterized by a river valley associated with another geographic feature or area.
-
C.
hasAncestralRiver
Indicates that an entity is associated with or originates from a river regarded as its ancestral or traditional source.
-
D.
hasRiverValleyType
Indicates that an entity (such as a river or geographic area) is characterized by or associated with a specific type of river valley.
-
E.
riverinePeople
Indicates a relationship where people live along, depend on, or are closely associated with rivers and river environments.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 30, 2026, 11:42 p.m.