Triple
T1353301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corps législatif of France |
E28930
|
entity |
| Predicate | hasNoPower |
P24117
|
FINISHED |
| Object | legislative initiative |
—
|
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: legislative initiative | Statement: [Corps législatif of France, hasNoPower, legislative initiative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoPower Context triple: [Corps législatif of France, hasNoPower, legislative initiative]
-
A.
hasNoPowerOver
chosen
Indicates that one entity lacks authority, control, or influence over another entity or situation.
-
B.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
C.
lostPower
Indicates that an entity has ceased to have electrical or functional power it previously possessed.
-
D.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
E.
lostPowerIn
Indicates that an entity has experienced a loss of electrical or functional power while in or at a specified location or context.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c26e916c8190b4b324df87f4c121 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef7700c819099b294e8d9320e70 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.