Triple
T11170304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copenhagen criteria |
E264255
|
entity |
| Predicate | politicalCriteriaInclude |
P36515
|
FINISHED |
| Object | democracy |
—
|
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: democracy | Statement: [Copenhagen criteria, politicalCriteriaInclude, democracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalCriteriaInclude Context triple: [Copenhagen criteria, politicalCriteriaInclude, democracy]
-
A.
evaluationCriteriaInclude
chosen
Indicates that certain criteria are part of, or explicitly included in, the set of standards used to evaluate something.
-
B.
politicalRequirement
Indicates that one entity imposes or must satisfy a political condition, qualification, or constraint in relation to another entity or context.
-
C.
eligibleFrom
Indicates that a subject becomes or is considered eligible starting from a specified point in time or condition.
-
D.
eligiblePersons
Indicates that certain persons meet the required conditions or criteria to qualify for a particular status, benefit, or participation.
-
E.
voterEligibilityCriterion
Indicates the rule or condition that determines whether an individual is allowed to vote in a given context.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8952e248190b0751669e8c960b7 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.