Triple
T612802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovak Assembly |
E12136
|
entity |
| Predicate | legislativeStructure |
P11711
|
FINISHED |
| Object | unicameral |
—
|
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: unicameral | Statement: [Slovak Assembly, legislativeStructure, unicameral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislativeStructure Context triple: [Slovak Assembly, legislativeStructure, unicameral]
-
A.
legislatureStructure
chosen
Indicates how a legislative body is organized, such as its internal composition, chambers, and structural arrangement.
-
B.
hasLegislatureType
Indicates the specific form or system of legislature that an entity possesses or operates under.
-
C.
legislativeBodyOf
Indicates that one entity is the official legislative body (lawmaking assembly) of another entity, typically a political unit such as a country, state, or city.
-
D.
legislature
Indicates that an entity serves as, or is part of, a law-making body or assembly responsible for creating or amending laws for a political unit.
-
E.
languageOfLegislature
Indicates the language or languages officially used by a legislature to conduct its proceedings, draft laws, and perform its formal functions.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49e08dbf88190ab050078a63e266b |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfa7b4481909bec7a5fd3e98c65 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.