Triple
T31441802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgian Constituent Assembly |
E802084
|
entity |
| Predicate | approvedConstitutionDate |
P2497
|
FINISHED |
| Object | 21 February 1921 |
—
|
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: 21 February 1921 | Statement: [Georgian Constituent Assembly, approvedConstitutionDate, 21 February 1921]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approvedConstitutionDate Context triple: [Georgian Constituent Assembly, approvedConstitutionDate, 21 February 1921]
-
A.
dateOfConstitutionSigning
chosen
Indicates the date on which a constitution was formally signed or adopted.
-
B.
lastConstitutionAdopted
Indicates that a particular constitution was the most recently adopted constitution of a given political entity or jurisdiction.
-
C.
dateOfPromulgation
Indicates the date on which a law, decree, or official act is formally proclaimed and put into effect.
-
D.
constitutionEffectiveFrom
Indicates the date or point in time from which a particular constitution or constitutional provision is legally in force and applicable.
-
E.
presidentialAssentDate
Indicates the date on which a president formally gives assent or approval to a law, decision, or official act.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: April 30, 2026, 9:06 p.m.