Triple
T37072823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolastoqiyik First Nations in New Brunswick |
E917626
|
entity |
| Predicate | riverColonialName |
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 First Nations in New Brunswick, riverColonialName, Saint John River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverColonialName Context triple: [Wolastoqiyik First Nations in New Brunswick, riverColonialName, Saint John River]
-
A.
colonialRiverName
chosen
Indicates that a river has or is associated with a name given during a colonial period, as opposed to its indigenous or pre-colonial name.
-
B.
riverAlsoKnownAs
Indicates that a river has an alternative name or alias by which it is also known.
-
C.
locatedOnTributaryOf
Indicates that one entity is situated along or on the banks of a tributary that flows into another specified water body.
-
D.
estuaryName
Indicates the naming relationship that assigns a specific name to an estuary.
-
E.
distributaryOf
Indicates that one watercourse branches off from a main river or stream and carries its water away, rather than feeding into 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:14 p.m.