Triple
T28545956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Alpnach |
E722436
|
entity |
| Predicate | hasBoatServices |
P36817
|
FINISHED |
| Object | Lake Lucerne Navigation Company |
—
|
NE NERFINISHED |
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: Lake Lucerne Navigation Company | Statement: [Lake Alpnach, hasBoatServices, Lake Lucerne Navigation Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoatServices Context triple: [Lake Alpnach, hasBoatServices, Lake Lucerne Navigation Company]
-
A.
hasBoatFacility
Indicates that an entity provides or is equipped with facilities or services specifically for boats.
-
B.
hasBoat
Indicates that one entity possesses, owns, or has control over a boat.
-
C.
hasMarinaService
Indicates that an entity provides marina-related services or facilities for boats and watercraft.
-
D.
boatService
Indicates that one entity provides or operates a transportation service by boat for another entity or between locations.
-
E.
hasBoatLine
chosen
Indicates that one entity operates, owns, or is associated with a particular boat service or boat route line.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 28, 2026, 3:39 a.m.