Triple
T32347688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitutional Court of the Czech Republic |
E826506
|
entity |
| Predicate | decisionIsFinal |
P176366
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Constitutional Court of the Czech Republic, decisionIsFinal, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionIsFinal Context triple: [Constitutional Court of the Czech Republic, decisionIsFinal, yes]
-
A.
hasFinalDecisionOn
Indicates that one entity holds the ultimate authority or responsibility to make and enforce a conclusive decision regarding another entity or matter.
-
B.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
-
C.
isFinalArbiterOf
Indicates that one entity has ultimate, authoritative decision-making power over another entity or over a particular matter, with no further appeal beyond that entity.
-
D.
finalDisposition
Indicates the ultimate outcome, status, or resolution assigned to an entity after all relevant processes or decisions are complete.
-
E.
decidedWith
Indicates that an entity made a decision jointly or in agreement with another entity.
- F. None of above. chosen
Provenance (4 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e029f0f88190b1f88d82a4a2cabd |
completed | May 3, 2026, 5:42 a.m. |
Created at: May 1, 2026, 12:49 a.m.