Triple
T36361964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Port d’Aix-les-Bains |
E895516
|
entity |
| Predicate | isPrincipalMarinaOn |
P194582
|
FINISHED |
| Object | Lac du Bourget |
—
|
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: Lac du Bourget | Statement: [Grand Port d’Aix-les-Bains, isPrincipalMarinaOn, Lac du Bourget]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrincipalMarinaOn Context triple: [Grand Port d’Aix-les-Bains, isPrincipalMarinaOn, Lac du Bourget]
-
A.
hasMarinaStatus
Indicates that an entity has a specific status or classification related to a marina (e.g., operational, planned, closed).
-
B.
marinaInstanceOf
Indicates that something is classified as an instance of the concept or type "marina."
-
C.
hasMarinaName
Indicates that an entity (such as a marina) is associated with a specific name identifying that marina.
-
D.
hasMarinaService
Indicates that an entity provides marina-related services or facilities for boats and watercraft.
-
E.
marinaOperator
Indicates that one entity operates, manages, or runs the marina facilities or services associated with another entity.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69fd7b042a548190b3abe31bc3258278 |
completed | May 8, 2026, 5:56 a.m. |
Created at: May 3, 2026, 4:09 p.m.