Triple
T17004238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayonet Constitution |
E412527
|
entity |
| Predicate | shiftedPowerTo |
P39302
|
FINISHED |
| Object | legislature |
—
|
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: legislature | Statement: [Bayonet Constitution, shiftedPowerTo, legislature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shiftedPowerTo Context triple: [Bayonet Constitution, shiftedPowerTo, legislature]
-
A.
laterPowerBaseShiftedTo
Indicates that the primary base of power or influence for an entity moved from one location or group to another at a subsequent time.
-
B.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
C.
shiftedUnder
Indicates that one entity has been moved or displaced to a position beneath another entity.
-
D.
shiftedAuthorityTo
chosen
Indicates that decision-making power or control has been transferred from one entity to another.
-
E.
expandedPowerTo
Indicates that one entity has increased or broadened authority, influence, or control over another entity or domain.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d380f968819097b59e7bac333ea4 |
completed | April 18, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.