Triple
T31910783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Momase Region |
E814677
|
entity |
| Predicate | includesRiverRegion |
P165
|
FINISHED |
| Object | Ramu River area |
—
|
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: Ramu River area | Statement: [Momase Region, includesRiverRegion, Ramu River area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRiverRegion Context triple: [Momase Region, includesRiverRegion, Ramu River area]
-
A.
riverRegion
Indicates that a river is located within, flows through, or is otherwise geographically associated with a particular region.
-
B.
isRegionalRiver
Indicates that a river is classified as a regional river, typically limited in geographic extent and significance to a specific region rather than being a major or national waterway.
-
C.
primaryRiverRegion
Indicates that a given region is the main geographic area through which a particular river primarily flows or with which it is chiefly associated.
-
D.
basinIncludesRegion
Indicates that a drainage basin or watershed spatially contains or encompasses a specified region within its boundaries.
-
E.
hasRiver
chosen
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a019579463c8190b51e39183b57bbaf |
completed | May 11, 2026, 8:38 a.m. |
| PD | Predicate disambiguation | batch_6a0192d309488190a3d86c93e7138c77 |
completed | May 11, 2026, 8:26 a.m. |
Created at: May 1, 2026, 12:01 a.m.