Triple
T23660209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peseux |
E584421
|
entity |
| Predicate | hasIntegrationType |
P8841
|
FINISHED |
| Object | municipal merger |
—
|
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: municipal merger | Statement: [Peseux, hasIntegrationType, municipal merger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntegrationType Context triple: [Peseux, hasIntegrationType, municipal merger]
-
A.
hasModeIntegration
Indicates that one entity is integrated with, or supports integration of, a particular mode, method, or modality of operation.
-
B.
isStateIntegrated
Indicates that an entity is formally incorporated into and functions as part of a larger state or governmental system.
-
C.
hasIntegratedUnit
Indicates that one entity includes another entity as a built-in or internally combined component or unit.
-
D.
hasIntegrationOrganization
Indicates that an entity is associated with or connected to a specific organization for the purpose of integration or interoperable collaboration.
-
E.
typeOfIntegration
chosen
Indicates the specific kind or category of integration that exists or is applied between systems, components, or processes.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b35f03448190834991c2a65ef0e4 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.