Triple
T9295601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic of New Granada |
E223629
|
entity |
| Predicate | constitutionReformed |
P49745
|
FINISHED |
| Object | 1843 |
—
|
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: 1843 | Statement: [Republic of New Granada, constitutionReformed, 1843]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constitutionReformed Context triple: [Republic of New Granada, constitutionReformed, 1843]
-
A.
constitutionalConvention
Indicates a formal gathering or assembly convened to draft, revise, or adopt a constitution or fundamental governing framework.
-
B.
constitutionalReformSubject
chosen
Indicates that an entity is the subject or focus of a constitutional reform process, proposal, or change.
-
C.
constitutionAdopted
Indicates that a particular constitution has been formally accepted and put into effect by the relevant authority or polity.
-
D.
constitutionType
Indicates the type or form of a constitution that characterizes or governs an entity.
-
E.
constitutionalReformCreatedBy
Indicates that a specific constitutional reform was initiated, drafted, or brought into existence by a particular actor or entity.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd089b44f88190a9bf76111355881d |
completed | April 1, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.