Triple
T4129494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Council |
E85004
|
entity |
| Predicate | establishedAsModernParliament |
P54011
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [General Council, establishedAsModernParliament, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsModernParliament Context triple: [General Council, establishedAsModernParliament, 1993]
-
A.
firstParliamentStart
Indicates the date or point in time when an entity’s first parliamentary term or session began.
-
B.
hasDevolvedParliamentSince
Indicates that a region or country has had its own devolved parliamentary body continuously since the specified time.
-
C.
oneOfOldestParliamentsIn
Indicates that the subject is among the oldest parliaments located in the specified place or jurisdiction.
-
D.
yearEnteredIntoForce
Indicates the year in which an agreement, law, treaty, or similar instrument officially became legally effective or operational.
-
E.
governmentInPowerAtEnactment
Indicates that a specific government or administration was the one holding power at the time a particular law, policy, or measure was enacted.
- 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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af01883b6c8190a482ead589a131a5 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af039fb19c8190b20e62a3b3ad25c1 |
completed | March 9, 2026, 5:30 p.m. |
Created at: March 9, 2026, 3:42 p.m.