Triple
T9682581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramu River |
E234320
|
entity |
| Predicate | basinPopulationActivity |
P89607
|
FINISHED |
| Object | subsistence agriculture |
—
|
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: subsistence agriculture | Statement: [Ramu River, basinPopulationActivity, subsistence agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basinPopulationActivity Context triple: [Ramu River, basinPopulationActivity, subsistence agriculture]
-
A.
populationConcentration
Indicates the degree to which a population is densely gathered or distributed within a specific area or region.
-
B.
hasBasinPopulation
Indicates that a geographic basin is associated with a specific number of inhabitants living within its area.
-
C.
hasPopulationConcentrationIn
Indicates that a population is densely or significantly clustered within a specified geographic area or region.
-
D.
populationFocus
Indicates that something is primarily directed toward, concerned with, or designed for a particular population or demographic group.
-
E.
populationDensity
Indicates the number of individuals or entities occupying a unit area within a given region.
- 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_69ca84c99e34819092e5563a7106cfca |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ccdbcc48190a4a9a70b3f419ac2 |
completed | April 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:16 p.m.