Triple
T31714271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolastoqiyik |
E809410
|
entity |
| Predicate | colonialRiverName |
P174432
|
FINISHED |
| Object | Saint John River |
—
|
NE NERFINISHED |
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: Saint John River | Statement: [Wolastoqiyik, colonialRiverName, Saint John River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialRiverName Context triple: [Wolastoqiyik, colonialRiverName, Saint John River]
-
A.
useRiverSystems
Indicates that an entity utilizes or manages river systems for a particular purpose or function.
-
B.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
C.
riverineLocation
Indicates that something is located in, along, or directly associated with a river or river system.
-
D.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
-
E.
associatedRiverBasin
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c2451e108190a73ccfdc99203d55 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: April 30, 2026, 11:16 p.m.