Triple
T7802451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muskrat Falls Generating Station |
E180461
|
entity |
| Predicate | distanceFromMouthOfRiver |
P56863
|
FINISHED |
| Object | approximately 25 km |
—
|
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: approximately 25 km | Statement: [Muskrat Falls Generating Station, distanceFromMouthOfRiver, approximately 25 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromMouthOfRiver Context triple: [Muskrat Falls Generating Station, distanceFromMouthOfRiver, approximately 25 km]
-
A.
riverMileFromMouth
Indicates the distance, measured in river miles, from the river’s mouth upstream to a specific point along the river.
-
B.
riverKilometerContext
chosen
Indicates the position or context of something along a river, measured in river kilometers from a defined reference point.
-
C.
riverLocation
Indicates that a river is located in, passes through, or is geographically associated with a specified place or region.
-
D.
waterwayLengthKilometres
Indicates the total length of a waterway, measured in kilometres.
-
E.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
- 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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:33 p.m.