Triple
T9710623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of the Czech Republic |
E235012
|
entity |
| Predicate | definesSovereign |
P90383
|
FINISHED |
| Object | people |
—
|
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: people | Statement: [Constitution of the Czech Republic, definesSovereign, people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesSovereign Context triple: [Constitution of the Czech Republic, definesSovereign, people]
-
A.
sovereignGovernment
Indicates that a government possesses ultimate authority and independence over a defined territory, free from external control.
-
B.
sovereigntyRegime
Indicates the type or structure of political authority and control exercised over a territory or population.
-
C.
sovereignComponent
Indicates that one entity functions as a constituent part of a larger sovereign whole, such as a state, polity, or authority.
-
D.
hasSovereignPowerOver
Indicates that one entity holds ultimate governing authority or supreme ruling power over another entity.
-
E.
recognizedAsSovereignWithin
Indicates that an entity is officially acknowledged as having sovereign authority or status within a specified domain, territory, or jurisdiction.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9da8eaa08190b3ba148d85c5cec5 |
completed | April 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:19 p.m.