Triple
T14377736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasaloppet |
E356517
|
entity |
| Predicate | finishLineLandmark |
P79515
|
FINISHED |
| Object | Mora Church vicinity |
—
|
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: Mora Church vicinity | Statement: [Vasaloppet, finishLineLandmark, Mora Church vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finishLineLandmark Context triple: [Vasaloppet, finishLineLandmark, Mora Church vicinity]
-
A.
hasLandmarkAtEnd
chosen
Indicates that a landmark is located at the terminal point or end of a specified path, route, or boundary.
-
B.
finalLineMeter
Indicates that the metrical pattern or structure of the final line of a text, verse, or utterance is being specified or characterized.
-
C.
mainLandmarkCreated
Indicates that one entity is the primary landmark that was created or established by another entity.
-
D.
frontLineReached
Indicates that an entity has arrived at or crossed into the designated front line or primary boundary of engagement.
-
E.
finishPosition
Indicates the final rank or place an entity achieves in an ordered outcome, such as a race, competition, or sequence of results.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900a67e08190ab1dcf36e6bb3405 |
completed | April 14, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.