Triple
T27414527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matane, Quebec |
E692854
|
entity |
| Predicate | isRegionalServiceHub |
P50530
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Matane, Quebec, isRegionalServiceHub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionalServiceHub Context triple: [Matane, Quebec, isRegionalServiceHub, true]
-
A.
isRegionalServiceCentre
chosen
Indicates that an entity functions as a regional service center responsible for providing services or support to a defined geographic area.
-
B.
hasRegionalServices
Indicates that an entity provides or is associated with services that operate within a specific geographic region or set of regions.
-
C.
isBorderRegionHub
Indicates that a region functions as a central node or key focal point for activities, connections, or services in a border area between territories.
-
D.
regionServedFromHub
Indicates that a particular region receives its services, operations, or logistical support from a specified hub location.
-
E.
isServiceCentreFor
Indicates that one entity functions as a service center that provides support, maintenance, or related services for another entity.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 12:33 p.m.