Triple
T26071942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Susitna North |
E657572
|
entity |
| Predicate | distanceToTalkeetnaInMiles |
P193820
|
FINISHED |
| Object | 27 |
—
|
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: 27 | Statement: [Susitna North, distanceToTalkeetnaInMiles, 27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToTalkeetnaInMiles Context triple: [Susitna North, distanceToTalkeetnaInMiles, 27]
-
A.
distanceToWasillaInMiles
Indicates the numerical distance, measured in miles, between a given entity’s location and the city of Wasilla.
-
B.
distanceToDenali
Indicates the measured or estimated spatial distance between a given entity and Denali.
-
C.
distanceFromAnchorage
Indicates the measured distance between a given location or object and Anchorage.
-
D.
distanceFromFairbanks
Indicates the spatial distance between a given location or entity and the city of Fairbanks.
-
E.
approximateDistanceFromAnchorage
Indicates the estimated spatial distance between a given entity and Anchorage, rather than an exact measured value.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fd57b9cdec81908536c4159e375931 |
completed | May 8, 2026, 3:25 a.m. |
Created at: April 26, 2026, 7:30 p.m.