Triple
T5301659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | royal veto of Louis XVI |
E119995
|
entity |
| Predicate | usedToBlock |
P43618
|
FINISHED |
| Object | decrees against émigré nobles |
—
|
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: decrees against émigré nobles | Statement: [royal veto of Louis XVI, usedToBlock, decrees against émigré nobles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToBlock Context triple: [royal veto of Louis XVI, usedToBlock, decrees against émigré nobles]
-
A.
canBlock
chosen
Indicates that one entity has the ability or permission to prevent, obstruct, or stop the action or effect of another entity.
-
B.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
C.
usedCross
Indicates that one entity made use of a cross-shaped object or structure, or traversed by means of a crossing point such as a crosswalk or intersection.
-
D.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
-
E.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
- 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_69bd44704be88190acdb2ac481b0ff55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8e44e7c881909b241b2fec366038 |
completed | March 20, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69bd845097ac81909678624c4907fda4 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:53 p.m.