Triple
T23831572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Lawrence River drainage basin |
E589525
|
entity |
| Predicate | outlet |
P29203
|
FINISHED |
| Object | Gulf of St. Lawrence |
—
|
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: Gulf of St. Lawrence | Statement: [St. Lawrence River drainage basin, outlet, Gulf of St. Lawrence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outlet Context triple: [St. Lawrence River drainage basin, outlet, Gulf of St. Lawrence]
-
A.
majorOutletOf
Indicates that one entity serves as a primary distribution or sales channel for another entity’s products or services.
-
B.
majorOutlet
Indicates that an entity functions as a primary or significant distribution or publication channel for another entity.
-
C.
hasOutlet
Indicates that one entity provides, contains, or is equipped with an outlet or point of access for another entity.
-
D.
hasOutletStores
Indicates that an entity operates or is associated with one or more outlet retail stores.
-
E.
locatedAtOutletOf
chosen
Indicates that one entity is positioned at or directly adjacent to the outlet or discharge point of another entity (such as a flow, channel, or system).
- 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f6f25c8190bd8957fe3cbefc03 |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:05 p.m.