Triple
T16544662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syndic of Monthey |
E401910
|
entity |
| Predicate | isStyleOfAddressFor |
P64298
|
FINISHED |
| Object | head of Monthey municipality |
—
|
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: head of Monthey municipality | Statement: [Syndic of Monthey, isStyleOfAddressFor, head of Monthey municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStyleOfAddressFor Context triple: [Syndic of Monthey, isStyleOfAddressFor, head of Monthey municipality]
-
A.
isStyleOfAddress
Indicates that one term or expression functions as a particular way of addressing or referring to another entity.
-
B.
usedInStyleOfAddress
chosen
Indicates that one entity is used as a form or style of address when referring to or speaking to another entity.
-
C.
typeOfAddress
Indicates the specific category or kind of address (e.g., home, work, billing) associated with an entity.
-
D.
addressingType
Indicates the manner or form in which one entity addresses or refers to another (e.g., formally, informally, by title, or by name).
-
E.
addressFormat
Indicates the standardized structure or pattern in which an address’s components are arranged and written.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34560daf08190b353b415d8ab280d |
completed | April 18, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.