Triple
T1884409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pic River |
E39928
|
entity |
| Predicate | drainsRegion |
P1559
|
FINISHED |
| Object | boreal shield |
—
|
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: boreal shield | Statement: [Pic River, drainsRegion, boreal shield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainsRegion Context triple: [Pic River, drainsRegion, boreal shield]
-
A.
drainsInto
Indicates that one entity serves as a source or conduit whose contents or flow are directed into another entity.
-
B.
drainageBasin
chosen
Indicates the area of land where all precipitation and surface water flow are collected and drained toward a particular river, lake, or other water body.
-
C.
drainageDivideOf
Indicates that one geographic feature functions as the drainage divide (separating water flow into different basins) for another feature or area.
-
D.
basinIncludesRegion
Indicates that a drainage basin or watershed spatially contains or encompasses a specified region within its boundaries.
-
E.
drainageType
Indicates the kind or classification of drainage associated with or applied to an entity (e.g., how water is removed or flows from it).
- 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_69a88633e4fc8190b7eb40463e048ec5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb4f53f408190ae30e1a12721e7d7 |
completed | March 7, 2026, 5:17 a.m. |
| PD | Predicate disambiguation | batch_69abafe497a88190a1da6af2888b71b4 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.