Triple
T18812683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Unicameral |
E460054
|
entity |
| Predicate | establishedAsUnicameral |
P57484
|
FINISHED |
| Object | 1937 |
—
|
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: 1937 | Statement: [The Unicameral, establishedAsUnicameral, 1937]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsUnicameral Context triple: [The Unicameral, establishedAsUnicameral, 1937]
-
A.
isUnicameral
Indicates that a legislative body consists of a single chamber or house, rather than multiple separate chambers.
-
B.
reorganizedAsUnicameralIn
chosen
Indicates that a previously different legislative structure was changed into a unicameral (single-chamber) system in a specified place or time.
-
C.
isUnicameralComponentOf
Indicates that a legislative body or chamber is a single-chamber (unicameral) part of a larger political or governmental system.
-
D.
hasBicameralStructure
Indicates that an entity possesses a two-chamber (two-house) internal organizational or legislative structure.
-
E.
hasUnicameralOrBicameralContext
Indicates that an entity is associated with a legislative context specifying whether it is unicameral or bicameral.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a3dcc7d88190801d9c9202e0e411 |
completed | April 20, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.