Triple
T31555591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loimaa municipal council |
E805117
|
entity |
| Predicate | hasPolicyAuthority |
P142632
|
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: [Loimaa municipal council, hasPolicyAuthority, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolicyAuthority Context triple: [Loimaa municipal council, hasPolicyAuthority, true]
-
A.
hasAuthorityOf
Indicates that one entity possesses and can exercise the official power, rights, or control that properly belong to another entity.
-
B.
hasPublicAuthority
chosen
Indicates that an entity possesses official power or legal authority to act on behalf of the public or a governing body.
-
C.
hasApprovalAuthority
Indicates that an entity possesses the power or right to review and formally approve or reject decisions, actions, or requests made by others.
-
D.
hasPolicyStatus
Indicates that an entity is associated with a policy and specifies the current status or state of that policy.
-
E.
hasAuthorityControl
Indicates that one entity possesses formal power, control, or decision-making authority over another entity or activity.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: April 30, 2026, 10:12 p.m.