Triple
T5252862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geatland |
E118628
|
entity |
| Predicate | travelRouteInBeowulf |
P24031
|
FINISHED |
| Object | sea voyage to Denmark |
—
|
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: sea voyage to Denmark | Statement: [Geatland, travelRouteInBeowulf, sea voyage to Denmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelRouteInBeowulf Context triple: [Geatland, travelRouteInBeowulf, sea voyage to Denmark]
-
A.
pilgrimageRouteTo
Indicates a route or path that is traditionally used or designated for making a religious or spiritual pilgrimage to a particular destination.
-
B.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
C.
popularRouteFrom
chosen
Indicates a frequently chosen or well-traveled route that starts from a given origin location.
-
D.
travelsThrough
Indicates that something moves along, passes across, or is routed via a particular path, medium, or location.
-
E.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b7cd7f4819098e591df07564a52 |
completed | March 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.