Triple
T33163410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boulevard de la Villette |
E848809
|
entity |
| Predicate | hasNearbyCanalBasin |
P173221
|
FINISHED |
| Object | Bassin de la Villette |
—
|
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: Bassin de la Villette | Statement: [Boulevard de la Villette, hasNearbyCanalBasin, Bassin de la Villette]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyCanalBasin Context triple: [Boulevard de la Villette, hasNearbyCanalBasin, Bassin de la Villette]
-
A.
nearbyCanal
Indicates that one entity is located close to or in the immediate vicinity of a canal.
-
B.
hasCanals
Indicates that one entity possesses or contains canals, either as physical waterways or channel-like structures.
-
C.
isLocatedNearBasin
chosen
Indicates that one entity is situated close to or in the immediate vicinity of a basin.
-
D.
hasNearbyWaterInfrastructure
Indicates that a location or entity is situated close to water-related infrastructure such as pipes, treatment facilities, or distribution systems.
-
E.
hasAdjacentCanal
Indicates that one entity is directly next to or alongside a canal.
- 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff6ef0d61c81909162d37c15a1a3c3 |
completed | May 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ff6c6a58e08190921317062cd9d489 |
completed | May 9, 2026, 5:18 p.m. |
Created at: May 1, 2026, 1:28 a.m.