Triple
T16965506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States federal system |
E411529
|
entity |
| Predicate | allowsConcurrentPowers |
P33660
|
FINISHED |
| Object | taxation |
—
|
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: taxation | Statement: [United States federal system, allowsConcurrentPowers, taxation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsConcurrentPowers Context triple: [United States federal system, allowsConcurrentPowers, taxation]
-
A.
hasNumberOfPowers
Indicates the quantity of distinct powers or abilities that an entity possesses.
-
B.
supportsMultiplePowerRoles
Indicates that an entity can simultaneously handle or be assigned more than one distinct power-related role.
-
C.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
D.
hasMultipleHoldersSimultaneously
chosen
Indicates that a given item, role, or resource is concurrently possessed, controlled, or occupied by more than one holder at the same time.
-
E.
restrictsPowerOf
Indicates that one entity limits, constrains, or reduces the authority, control, or influence that another entity can exercise.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0a3cecc8190a490573adce80cca |
completed | April 18, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:31 a.m.