Triple
T20809549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moosonee |
E512260
|
entity |
| Predicate | distanceToMooseFactoryByRiver_km |
P141914
|
FINISHED |
| Object | about 5 |
—
|
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: about 5 | Statement: [Moosonee, distanceToMooseFactoryByRiver_km, about 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMooseFactoryByRiver_km Context triple: [Moosonee, distanceToMooseFactoryByRiver_km, about 5]
-
A.
distanceFromBrowseBasin_km
Indicates the distance, measured in kilometers, between an entity and the Browse Basin.
-
B.
waterwayLengthKilometres
Indicates the total length of a waterway, measured in kilometres.
-
C.
riverKilometerContext
Indicates the position or context of something along a river, measured in river kilometers from a defined reference point.
-
D.
riverMileFromMouth
Indicates the distance, measured in river miles, from the river’s mouth upstream to a specific point along the river.
-
E.
distanceFromMossman
Indicates the measured or specified distance between a given entity or location and Mossman.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d199888190b8b190c928f510b7 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:40 p.m.