Triple
T31563124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edistyspuolue |
E805324
|
entity |
| Predicate | supportedPrinciples |
P9935
|
FINISHED |
| Object | civil liberties |
—
|
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: civil liberties | Statement: [Edistyspuolue, supportedPrinciples, civil liberties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedPrinciples Context triple: [Edistyspuolue, supportedPrinciples, civil liberties]
-
A.
supportsPrinciple
chosen
Indicates that one entity endorses, upholds, or actively backs a particular principle or doctrine.
-
B.
providesPrinciplesFor
Indicates that one entity supplies the foundational rules, guidelines, or theoretical basis that another entity follows or is built upon.
-
C.
implementsPrinciple
Indicates that an entity applies, follows, or puts into practice a specified principle in its design, behavior, or operation.
-
D.
typeOfPrinciples
Indicates a relationship where one entity specifies the kind or category of principles that another entity embodies, uses, or is governed by.
-
E.
usesPrinciple
Indicates that one entity applies, relies on, or is based upon a particular principle in its functioning, reasoning, or design.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:16 p.m.