Triple
T26921668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Sept-Îles |
E677661
|
entity |
| Predicate | hasHarbourNameOrigin |
P3325
|
FINISHED |
| Object | named after the town of Sept-Îles |
—
|
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: named after the town of Sept-Îles | Statement: [Port of Sept-Îles, hasHarbourNameOrigin, named after the town of Sept-Îles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHarbourNameOrigin Context triple: [Port of Sept-Îles, hasHarbourNameOrigin, named after the town of Sept-Îles]
-
A.
harbourNamedBy
Indicates that a harbour bears a particular name as designated or assigned by a specific source or naming authority.
-
B.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
C.
harbourName
Indicates the name assigned to a harbour in which an entity is located or associated.
-
D.
harbourAlsoKnownAs
Indicates that a harbour is referred to by an alternative name or alias.
-
E.
hasAncestralHarbour
Indicates that an entity has a harbour that historically served as the origin or ancestral port associated with it.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 6:07 a.m.