Triple
T34852965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ville Close |
E1004649
|
entity |
| Predicate | locatedInHarborOf |
P87968
|
FINISHED |
| Object | Concarneau harbor |
E620475
|
NE 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: Concarneau harbor | Statement: [Ville Close, locatedInHarborOf, Concarneau harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInHarborOf Context triple: [Ville Close, locatedInHarborOf, Concarneau harbor]
-
A.
locatedInHarbourArea
chosen
Indicates that something is situated within the geographic or administrative boundaries of a harbour area.
-
B.
hasNearbyHarbor
Indicates that one location has a harbor situated close to it in geographic proximity.
-
C.
isPortOfCallFor
Indicates that a location serves as a scheduled stop or destination for a ship, vehicle, or journey.
-
D.
isMainHarbourOf
Indicates that a harbour serves as the primary or principal port facility for a specified location or region.
-
E.
mooredAt
Indicates that one object, typically a vessel or floating structure, is secured or anchored at a specific location or facility.
- F. None of above.
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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3786cea29081908ca42e59b082957b |
completed | June 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.