Triple
T31118790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EU Article 7 procedure against Poland |
E793165
|
entity |
| Predicate | valueConcerned |
P64698
|
FINISHED |
| Object | respect for the rule of law |
—
|
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: respect for the rule of law | Statement: [EU Article 7 procedure against Poland, valueConcerned, respect for the rule of law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueConcerned Context triple: [EU Article 7 procedure against Poland, valueConcerned, respect for the rule of law]
-
A.
concernedProperty
Indicates that one entity is about, involves, or pertains to a particular property or attribute of another entity.
-
B.
subjectOfConcernFor
Indicates that one entity is regarded as a matter of worry, interest, or attention for another entity.
-
C.
targetConcern
chosen
Indicates that something is the specific issue, problem, or subject that is the focus of attention, action, or consideration.
-
D.
concernedSee
Indicates that one entity looks at or observes another with a sense of worry, care, or concern.
-
E.
concern
Indicates that one entity is about, relates to, or is of interest or importance to 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 29, 2026, 9:04 p.m.