Triple
T27052585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koraleigh |
E684811
|
entity |
| Predicate | distanceToMajorRiver |
P198671
|
FINISHED |
| Object | near Murray River |
—
|
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: near Murray River | Statement: [Koraleigh, distanceToMajorRiver, near Murray River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMajorRiver Context triple: [Koraleigh, distanceToMajorRiver, near Murray River]
-
A.
riverTypeNearby
Indicates that one entity is located near a river of a specified type or classification.
-
B.
nearestMajorRiverTown
Indicates that one town is the closest significant river-based settlement to another location or town.
-
C.
hasApproxLengthAlongRiver
Indicates that an entity has an approximate measured length that follows the course of a river rather than a straight-line distance.
-
D.
distanceToMooseFactoryByRiver_km
Indicates the distance in kilometers to Moose Factory when traveling along the river route.
-
E.
riverLocation
Indicates that a river is located in, passes through, or is geographically associated with a specified place or region.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
| PDg | Predicate description generation | batch_69fefb13eb288190bcfae0541cfd7b98 |
completed | May 9, 2026, 9:15 a.m. |
Created at: April 27, 2026, 8:15 a.m.