Triple
T21922439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | liberum veto |
E541351
|
entity |
| Predicate | statusAfter1791 |
P146571
|
FINISHED |
| Object | formally abolished in most legislative matters |
—
|
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: formally abolished in most legislative matters | Statement: [liberum veto, statusAfter1791, formally abolished in most legislative matters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfter1791 Context triple: [liberum veto, statusAfter1791, formally abolished in most legislative matters]
-
A.
statusAfter1799
Indicates the condition or state of something as it existed after the year 1799.
-
B.
statusBefore1789
Indicates the status or condition that an entity had prior to the year 1789.
-
C.
statusAfter1871
Indicates the status or condition of an entity as it exists after the year 1871, typically in contrast to its prior status.
-
D.
statusAfter1815
Indicates the status or condition of an entity as it existed after the year 1815.
-
E.
statusAfter1814
Indicates the condition or standing that an entity has in the period following the year 1814.
- 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1233d096c8190af0d7cd21879c91b |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
| PDg | Predicate description generation | batch_69e6fb6991948190a428c3c3bfd1c3b8 |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 7:45 p.m.