Triple
T2032681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States in Congress Assembled |
E44552
|
entity |
| Predicate | lacksPower |
P33154
|
FINISHED |
| Object | levy direct taxes on individuals |
—
|
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: levy direct taxes on individuals | Statement: [United States in Congress Assembled, lacksPower, levy direct taxes on individuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lacksPower Context triple: [United States in Congress Assembled, lacksPower, levy direct taxes on individuals]
-
A.
hadNoPower
chosen
Indicates that an entity lacked authority, control, or ability to act or influence in a given situation or context.
-
B.
hasNoPowerOver
Indicates that one entity lacks authority, control, or influence over another entity or situation.
-
C.
lostPower
Indicates that an entity has ceased to have electrical or functional power it previously possessed.
-
D.
lostPowerIn
Indicates that an entity has experienced a loss of electrical or functional power while in or at a specified location or context.
-
E.
lostPowerAgainIn
Indicates that an entity has experienced a repeated loss of power in 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb93255248190bd47a54a7b3c7447 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.